Pricing Management Software Kenya

Yes. The price the system resolves at order placement flows straight to the invoice in KES, so the value published to KRA eTIMS matches the rate the duka or supermarket chain was billed against.

Yes. Customer Type lists hold one rate set for supermarket chains, another for tier-1 distributors, another for wholesalers, dukas, and HoReCa. Each channel class sees its own KES rate at order placement.

Configured in Settings > Pricing. The platform checks customer-specific list, then customer-type list, then geography list, then the SKU fallback. The first active list inside its Valid From and Valid To window wins.

Fallback Price Settings hold the safety net. Primary sales fall back to MRP, Selling, or Cost from the SKU master. Secondary sales carry their own fallback, so duka orders never bill at a primary tier rate.

Yes. Geography Based lists attach a rate set to any node in the geography hierarchy, so a SKU can post one KES rate for Nairobi outlets and a different one for Mombasa, Kisumu, or upcountry routes.

Yes. Create Price List exposes Bulk Upload, so KEBS-listed SKU rates and large customer sets load from a single Excel template. Brands skip per-row entry and onboard distributor networks in one pass.

Every list carries Active status, Valid From, Valid To, and the user who edited it. The cards and table on the Pricing screen surface Total, Active, Inactive, and Customer Specific counts, giving finance a clean audit trail.

Yes. The Pricing module runs fully on cloud with no on-premise setup. The web portal serves pricing managers, the mobile app serves field reps, and rates sync in real time across both. Onboarding is remote.