Routing and sales status control

Period  — 

The same fruit is labeled with different variety, weight, count and grade at each supplier. Each sales option shows its current purchase route and alternatives, and the operator can pin, prefer or hold a route. Only products whose specs match exactly are chosen, not candidates with similar names. Options that lose their purchase route stop selling and reopen when a route comes back.

Picks the supplier whose specs match each sales option exactly,
and pauses sales when no purchase route is left

GoPostgreSQLTypeScriptNext.js

  • Routing policy with PIN, PREFER and HOLD plus candidate exclusions on top of automatic selection
  • Matching that identifies the same product by item, variety, weight, count, grade, size and channel option IDs
  • Fallback from expired preferred routes to the remaining eligible candidates
  • Automatic sales pause for options that lose their purchase route, and resumption once it recovers
  • Per‑channel relisting thresholds and stock maintenance for options the operator turned on

Matching products that names alone could not identify

Problem
Channel weight labels and supplier count rules differed, and variety aliases and grade names varied by supplier.
Solution
Channel weight and purchase count rules are stored separately, with rules for variety aliases and merged grades. Routes are chosen by the specs of what the customer ordered. Orders do not go to supplier products that only look similar by name.

Scattered options from past orders

Problem
Placeholder options from past Coupang orders made one sales option appear as several.
Solution
Placeholders were grouped under Coupang's immutable option IDs to clean up the option list.

Options that kept selling without supply

Problem
Options with no purchase route after a supplier sold out could keep selling on the sales channel.
Solution
Options that lose their purchase route stop selling automatically and reopen when a route returns. Sales status changes only on an operator action or a lost route.

Choices that could not be explained later

Problem
Candidate lists kept changing, so there was no way to explain later why a past order went to a given supplier.
Solution
The evidence at selection time is kept as an immutable record, and current candidates are stored separately.