Outlets, Price Lists, and Orders
The rep places an order under the outlet’s current terms. The warehouse receives quantities and approved substitutions, while the account manager sees what was ordered versus shipped.
Custom Development
Sales reps need each outlet’s terms, and the warehouse needs confirmed order lines. We’ll build a CRM that ties visits, prices, availability, and shipments to the customer and contract.
These modules can be included in the project. We’ll agree on the scope and workflow rules after reviewing your processes.
The rep places an order under the outlet’s current terms. The warehouse receives quantities and approved substitutions, while the account manager sees what was ordered versus shipped.
The manager sees actual quantities by order line and any substitution approvals. The difference between ordered and shipped quantities stays open until reconciled.
A price is tied to an outlet, validity period, and agreed terms. When the chain changes its price list, the rep sees when the new version takes effect.
How teams can divide responsibilities and handle exceptions after rollout.
The warehouse confirms available quantity and flags the shortage. The rep agrees on a partial shipment, a substitution, or a new date with the store.
The manager creates a price list version for the affected outlets. Confirmed orders retain their previous price, and new orders use the updated terms from the agreed date.
We’ll start with one rep’s route and agree how customer groups, outlets, and contracts are represented in the system of record. The rep creates the order, the warehouse confirms stock, and finance checks receivables. The pilot covers a partial shipment and an exceptional price.
The warehouse can continue to use its inventory system. The CRM gives reps the approved terms for an outlet and lets managers track refusals, partial shipments, and follow-ups.
Once we agree on the requirements, we design the screens, build a pilot, and try it against the agreed use cases. We plan the rollout and follow-on modules with your team.
Discuss the First PhaseA customer or contract can have a price list with a validity period. Each order retains the price applied even if the list changes later.
Integration depends on the available interfaces. Before implementation, we’ll define what counts as available stock and when reps should see it.
If the source system provides shipment items and quantities, the CRM can match them to order lines and show what remains to be shipped.
We’ll first match the purchasing entity, store addresses, contracts, and SKUs to the system of record. The trial import will cover a customer with several outlets and price lists. Duplicates and unknown SKUs go to review before launch.
Scope depends on the number of stock and payment sources, pricing rules, returns, and whether reps need mobile or offline access. For an estimate, share a chain’s price list, an order with a partial shipment, and the discount approval process.
To start, share one outlet’s terms, a typical order, and an example of a partial shipment.