For ecommerce
Delivered when the page said.
vertex sources each online order from the store or distribution centre that has the units and can make the promise, inside your rules. The locations it turned down stay on the record, with the reason.
3 screens, 3 answers, 1 jacket.
You can read a sell-out coming in the first hours of a launch. The rest of the week goes to asking the site, the stores and the warehouse how many there really are.
The queue
Website, marketplace and phone orders, each in its own list.
The promise
Next day on the product page, and no view of which building has to keep it.
The shared shelf
The site shows 3. A store sold 2 of them this morning.
The returns
Parcels come back wherever the customer sent them. The count catches up later.
The sell-out
A launch clears by lunch because nobody shared how deep the line was.
Before merchmix, a mid-market retailer runs on 10+ systems and 50+ spreadsheets.
Trouble surfaces before the customer writes.
Orders from every channel land in one workspace, phone and email included. Carrier scans flag the parcels likely to miss the promise while there is still time to act.
| Order | Channel | Value | Status | Fulfilment | Promise |
|---|---|---|---|---|---|
| ORD-200013Ana Silva | eBay | $45.00 | Dispatched | In transit | On track |
| ORD-200011Ruby Anderson | Shopify | $99.95 | Released | Allocated | On track |
An order needs holding.
Hold, release or cancel it where the order lives, with the customer’s history beside it.
A store comes up short.
The picker records what is there. The work carries on, or goes back to be sourced again.
A parcel stalls at the hub.
It becomes work with an owner, a priority and the clock running.
A return comes back.
orbit authorises it, receives it, inspects each line and records restock or quarantine.
Shops and site count the same units.
Available, held, low-safety and inbound, by SKU and location, live in seconds. vertex claims each unit as it promises it, so the last jacket is promised once.
Inbound shows as expected, arriving or overdue, so the page can promise what is on the way.
Thin lines get refilled early.
yukti reads live sales and stock, proposes the rebalance between stores and raises the replenishment, inside rules you set. You approve, or let it run. The store that ships online keeps units to promise.
Nothing leaves your queue as an export.
Marketing checks depth before a send. The warehouse picks at the location vertex chose. Ship an order and the plan already knows.
You still write the promise.
If sourcing and the promise run on their own, does the channel need someone running it? Yes. The rules are yours: which locations take online orders, which goes first, what the page can promise. So is the calendar. And the exceptions never stop.
vertex and yukti
- Choose the location.
- Claim the unit.
- Flag the late parcel.
- Propose the move.
You
- The rules of the promise.
- The calendar of launches and sends.
- The exceptions.
Questions, answered.
Does vertex replace the storefront?
No. Your storefront takes the order and the payment. vertex sources it, tracks it to the door and keeps its status, holds and cancellations.
Can I see why an order shipped from a store?
Yes. Each sourcing decision keeps the ranked candidates, the locations it rejected and the reason.
Can a store stop taking online orders?
Yes. Each location carries whether it accepts orders, with its own operating calendar and delivery coverage.
Does vertex create shipping labels or settle refunds?
No. Labels stay with your carriers and refunds with your payment provider. vertex tracks carrier scans against the promise.
How long until it is live?
Live in 12 to 15 weeks, end to end. Start with a free 6-week POC on your own data, with no contract.
A dress rehearsal before peak.
Put merchmix through a free 6-week POC on your own data before the busiest weeks of the year arrive.
- 1 hour
- A demo with sales and product.
- 6 weeks
- A free POC on your own data, no contract.
- 12 to 15 weeks
- To live, end to end.
Updated 21 October 2026