ERP for wholesale distribution

Define the promise the salesperson is allowed to make

A distributor's order promise depends on more than current stock. Record reserved quantities, held stock, expected receipts, transfer stock and demand from other channels. Decide what a salesperson can commit immediately and what requires buyer or warehouse review. Include different customer priorities and orders that must ship complete. Demonstrate a promise made before a supplier delay, then inspect how the change reaches sales and the customer-service queue. The application should distinguish an estimated inbound date from a confirmed, usable receipt. Ask where the authoritative promise lives when ecommerce, EDI or a portal is involved. A single stock number shown in several systems is insufficient evidence if their timing and reservation rules differ. The goal is a defensible commitment with a visible basis, not merely a fast quote screen.

Get the unit model right before judging speed

Distributors buy, store, pick and sell in different packs. Prepare an item purchased by carton, held as individual units and sold by both pack and piece. Add an item whose pack size changes by supplier. Demonstrate a broken carton, a partial return and a price expressed per hundred units. Verify barcodes and conversion precision on the actual receiving and picking device. Illustrative example: ten cartons contain 12 pieces each, while an order requests three packs of four and seven loose pieces. The correct physical issue is 19 pieces, leaving 101 before other movements. These are fictional test quantities. Ask finance to reconcile unit cost and the sales unit on the invoice. A fast scan that interprets a carton as a piece can create an apparently efficient workflow with systematically wrong availability and margin.

Test pricing as a controlled hierarchy

Build a small price pack containing a customer contract, a quantity break, a time-limited promotion and a manual exception. Ask which rule wins, who may override it and how the decision is visible later. Include a credit note and a replacement shipment. Do not compare only the number of price-list fields; compare whether staff can explain the offered price and whether an approval is needed for the unusual case. Track freight, handling, supplier rebates or other commercial elements only where the business actually uses them and with finance-approved treatment. Margin should be interpreted with its included costs and timing visible. A supplier rebate expected later is different from realized transaction margin. Require the proposal to explain any separate pricing or rebate application and who maintains the rules across channels.

Walk the warehouse with exception data

Run receiving, putaway, replenishment, picking, packing and shipment using a realistic bin structure. Include an overdelivery, a damaged case, a short pick and an urgent transfer. Observe whether an operator can resolve the issue within the assigned role or must call someone with unrestricted access. Ask how a count interacts with open tasks and how pick-face replenishment avoids double allocating stock. If a specialist WMS is proposed, delay an acknowledgment and replay a message. Check the stock result, not merely the interface status. Evaluate labels, scales and carrier connections with the physical device class that will be deployed. A desktop walkthrough can establish transaction logic but cannot establish that the aisle workflow is usable. Keep the first acceptance pack small enough to repeat after warehouse layout or integration changes.

Compare replenishment policies by item behavior

Some products merit stocked replenishment, others should be bought to order, and intermittent spares may need a separate review. Classify a sample of fast-moving, seasonal, new and erratic items. Ask how the planner sees the reason for a suggestion and overrides it. Odoo's official reordering documentation describes minimum and maximum quantities and purchase multiples. That is one documented replenishment mechanism, not a forecast-performance claim. Test supplier lead times, minimum order value or pack multiples as required by your operation. Include a substitute item and a transfer between warehouses. Check whether stock at a remote location is truly available before counting it against local demand. The useful output is a buyer's action list with supplier, quantity, date, demand basis and exceptions, rather than a mass of suggestions accepted without review.

Preserve identity through partial shipments and returns

Create an order with one line shipped now, one backordered and one supplied directly by a vendor. Follow the order into invoicing and a subsequent return. Determine who owns goods at each stage under the business's terms and which event creates the financial record. When tracked goods return, inspect their lot or serial identity and release status before resale. For a customer returning an equivalent item purchased elsewhere, make the policy and approval visible rather than silently restoring it to saleable stock. Include restocking charges, damaged returns and credit approval if relevant. The test should show what customer service sees while a warehouse return is physically present but finance has not issued a credit. An order status that says complete may hide several unresolved operational and commercial obligations.

Reconcile landed cost and channel economics

A receipt can arrive before freight or other directly attributable charges are finalized. Ask finance to demonstrate its approved cost process and show how a later charge affects stock and sold quantities in the selected configuration. Do not prescribe an accounting policy through the software evaluation. Include currency changes and partial receipts when they matter. Compare order economics with pick, pack and shipping effort visible enough for the business decision; adding every possible overhead allocation can make an apparent precision nobody can maintain. Deliver an availability rulebook, unit map, price hierarchy, warehouse exception pack, replenishment sample and return reconciliation. Use these artifacts to compare the whole proposed operating package, including ecommerce, EDI, WMS and carrier connections. The fit question is whether the team can make credible promises and preserve margin evidence through routine exceptions without creating a parallel stock ledger in spreadsheets.

The industry acceptance brief

Failure modes to investigate

• Publishing one stock number without defining reservations, held goods and expected receipts.
• Treating a carton barcode as interchangeable with a piece barcode.
• Using headline gross margin without stating freight, rebate and cost timing assumptions.
• Testing warehouse speed only with perfect picks and no replenishment conflicts.
• Restoring every returned item directly to saleable stock before inspection and authorization.

Questions buyers ask

Product dossiers to investigate

A research shortlist, not a quality ranking or confirmation of every industry requirement. Read the dossier and validate the actual proposal.

Continue the buying process