Marketplace and stock integration
Orders from every marketplace arrive in one system, stock is recalculated once and sent back out. The same unit does not get sold twice.
- Buildfrom $2,150
- Timeline2–3 weeks
- Supportfrom $420/mo
Who this suits: Sellers on several marketplaces where stock is edited in each cabinet separately and a cancellation for lack of goods costs the rating.
What is in the first version
- one order list
- a barcode matrix
- reserve on order
- priority stock push
The figures above are the package this sits on: Integration and data pipeline. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
An order becomes a reserve
The order places a reserve in the same second it arrives, not on the next push.
- 02
The item matches on a barcode
The shared key is the barcode, and a bundle writes off the items it is made of.
- 03
The new figure travels back out
The push queue runs by priority: first what is near zero and moving fast, then the long tail.
What decides whether this works or annoys people
Overselling happens between the pushes
The cure is not pushing more often but a buffer on fast movers: the last few units stay off the storefronts.
Two warehouses are two different figures
Goods in a marketplace warehouse are not yours to move, so the two schemes stay apart in the data, never summed.
A cancellation returns goods later
The status arrives before the goods do, so a return enters stock on receipt rather than on the event.
What to measure once it is live
- cancellations for lack of goods
- time from an order to the reserve
- items disagreeing at a stocktake
- pushes the marketplace refused
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Talking to the marketplacesPythonFastAPIGoTemporalRedis
- Stock and ordersPostgreSQLDockerS3Grafana
- The warehouse screenTypeScriptReactNext.js
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- hosting for the exchange and stock records
- paid seller cabinet plans
- a scanner, a thermal printer, labels
- licences for your inventory system
Asked before the first call
- We have no inventory system, stock lives in a spreadsheet. Does this fit?
- It fits, and a spreadsheet is usually the first source: imported once, after which stock lives in the system. What a spreadsheet never holds is batches, expiry dates and bin locations.
- How many marketplaces at once, and how expensive is adding another?
- As many as you run today, because the second marketplace is the whole point. Adding the next is a connector and new columns in the matrix, and we name its price before signing.
- How long before stock updates on the marketplace?
- The reserve inside the system is immediate; the storefront updates in whatever time the marketplace allows. We name that interval per marketplace before the build and measure it after launch.