Per-variant per-location
Each variant has stock at each location. Auto-created when a variant is added.
Multi-location inventory
Inventory that knows where every unit lives.
Track stock per variant per location. Transfers logged in a ledger. Checkout picks the right fulfillment location automatically. Built into the POS + ecom stack — no plugin.
Multi-store retailers usually stitch together a POS + an inventory tool + a third-party app to keep stock in sync. Vertex does all three.
multi location inventory softwaremulti store inventory managementwarehouse and store inventoryretail inventory across locationsinventory sync software
Backed by the full platform
Every feature you'd build yourself, ready out of the box
One platform spans every storefront, every channel, every back-office workflow — so the retail stack you launch tomorrow doesn't dead-end at 50 customers.
AI Storefront Builder
Paste a URL → live preview in 60s
Multi-vertical
Restaurant · Retail · Ecom · Services · Dispensary
App marketplace
OAuth 2.0 surface + theme app blocks
Stripe Connect
Apple Pay · Google Pay · Terminal
Translations + currencies
i18n + multi-currency built in
Multi-location inventory
Stock across stores + warehouses
Core capabilities
Operational controls that actually matter
A single operations layer keeps customer experience and back-office workflows aligned.
Inventory ledger
Every sale, return, transfer, manual adjustment recorded. Idempotent against webhook retries.
Fulfillment routing
Online orders route to the location that has stock + can ship cheapest to the customer.
Five location types
store, warehouse, popup, virtual, dropship — each with own ships/picks-up flags.
Workflow
From setup to daily execution
Sequence operations in a way teams can follow under real volume.
Add locations under Commerce → Locations.
Set per-variant per-location stock.
Customer orders auto-route to best location.
Audit movements via inventory ledger.
FAQ
Common buyer questions
Does this support transfers between stores?
Yes — transfer_in and transfer_out movements get logged with source + destination, fully auditable.
What happens on a refund?
Restock movement is logged with the same event-key pattern. Optional auto-restock or admin review depending on the refund type.
Get started
Launch your retail stack
Start with a prefilled signup flow and compare additional buyer guides before rollout.