Trade & retail

Wholesale

Wholesale ledgers are hard because of customer tiers, layered pricing, and payment terms. The same SKU carries different prices for different buyers, and goods often ship before the order is entered—the system has to tolerate that reality.

Cluster Trade
Focus Procurement · stock
Delivery Gate by gate, acceptable and operable

How we see this industry

Customers and ladder prices

Wholesale is not retail scaled up. Customers have grades, prices have layers, terms have length; the same SKU can price differently for A and B today. Sales often ship first, then backfill the order, then change price, then ask for terms. If the system only allows “order then ship, price from the list,” the floor will WeChat the order and Excel the receivables. We start from that reality: contract price, temporary specials, and quantity breaks can coexist; specials need approval and an expiry; ship-then-order is allowed, but the backfill must match lot and quantity and cannot hang forever.

Terms and receivables

Terms and receivables are where wholesale actually takes risk. Who may buy on account, how much, and how overdue stock is stopped cannot live in the owner’s memory. After we connect incoming payments, each customer gets a statement; overdue flags sales and finance; shipments consume credit and receipts release it. Reconciling is by order, truck, and discount—not once at month-end. Price rights split by role: a salesperson sees their own customer prices, cannot edit the company list at will, and a change keeps before/after values and an approver.

Sellable stock

Stock must split sellable, in transit, and already held. Wholesale warehouses often have several customers chasing one lot. A single “on hand” number lets sales sell the same lot twice. Physical, held-unshipped, inbound PO, and damaged must be separate; opening an order holds stock, cancel or return releases it. Purchasing should suggest from stockouts and customer orders, not a buyer’s feel. Multi-warehouse transfers, van sales, and returns into damaged stock all hit the same books or month-end counts never match.

Van sales and swaps

Van sales, placing stock, returns and swaps are the daily path, not exceptions. Goods on a salesperson’s truck are inventory and come back by lot; a refusal or spec swap must split from the original order instead of opening an unexplained payable. If promotions, rebates, and year-end kickbacks live only in a PDF contract, finance computes them in December and in-year margin is fiction. We put what can go into unit price into unit price and the rest into expense lines—both hang on the customer and the period.

Price policy first

Go-live order is usually customer files and price policy first, then order and ship, then receivables and purchase suggestions. Historical arrears must migrate and be checked—not only items. Training is sales, order clerks, and warehouse—if any of the three stay outside the system, the books split again. The goal is specific: same customer, same SKU, same terms, sales, warehouse, and finance see the same fact.

Typical scenarios

Tiered and negotiated pricing

Prices by customer tier, region, and annual volume, with negotiated quotes on their own approval path and pricing rules sales cannot edit.

Ship first, enter later

Counter and phone orders ship first and get entered afterwards; the ledger still has to add up rather than rely on memory.

Terms and statements

Monthly statements generate automatically, with unpaid, part-paid, and return offsets visible in one view.

Common blockers and how we handle them

Blocker

Price lists live in a few people's spreadsheets, anyone can edit them, and nobody knows when they change

How we handle it

Prices are maintained by tier and customer in the system, changes leave a record, and sales can select but not edit.

Blocker

On-screen stock is off from what is in the warehouse, and overselling ends in apologies

How we handle it

In-transit, reserved, and sellable quantities are tracked separately, orders check sellable stock, and count variances go through their own adjustment flow.

Blocker

Returns and exchanges are logged in a notebook and never reconcile at month end

How we handle it

Return notes link back to the original order, stock returns by lot, and offset entries are generated for finance.

Common system modules

Customers and tiers

Customer records, tiers, credit limits, and negotiated prices in one place.

Products and units

Case, unit, and bulk conversion, with barcodes and legacy codes side by side.

Purchasing and receiving

Purchase orders, receiving variances, and supplier statements connected.

Stock and transfers

In-transit, reserved, and sellable tracked per warehouse, with transfers.

Sales and backorders

Ship-first entry, partial shipment, and backorder tracking.

Statements and terms

Monthly statements, payment logging, and return offsets.

Delivery gates

  1. Scope

    Write down customer grades, contract prices, terms, and the real ship-then-order practice. Split what this phase must enter the system from what stays manual.

  2. Architecture

    Fix price policy, hold rules, and receivable definitions. Confirm how orders, warehouse, incoming payments, and current finance connect.

  3. Build & integrate

    Connect order, ship, and backfill on real customer prices and stock. Special-price approval, credit holds, and statements are acceptance items written first.

  4. Launch & operate

    Migrate customer files and open arrears first; train sales, order clerks, and warehouse. Pilot on active accounts; iterate next on purchase suggestions.

Related capabilities

Related industries

Industries we ship in

Walk us through your process before anything gets built

Tell us how the work happens today, where it breaks, and when you need it live. We will come back with a scope you can check and a phasing plan.

Contact Us

Email
service@wehoope.com
Phone
+86 139-2520-6166
Address
W903, Shenzhen-Hong Kong Industry-Education-Research Base, 201 Gaoxin South 7th Road, Nanshan District, Shenzhen