How can I connect stock across my shops and website?
Choose one authoritative inventory record, consistent product and variant codes, and clear rules for reservation, sale, cancellation, transfer and return. Connect channels through supported integrations, with a reconciliation process for failures. Display stock customers can actually receive, rather than the total physically present across every location.
The key idea
An inventory integration is dependable when the team can explain every stock movement and resolve a mismatch.
Give the same product the same identity everywhere
Start with a product catalogue your shop, warehouse and website agree on. A shirt style, colour and size may each affect the stock item. Use stable codes for actual variants and decide how bundles are counted. A product name alone is a fragile connection because spelling and translations change.
Worked example: the Arabic website calls an item “blue large shirt”, the POS uses a short English name and the warehouse uses a supplier code. Map them to one internal variant, then test a sale and a return. Record pack sizes and units so a carton is not treated as one individual piece.
Separate what is present from what can be promised
Physical stock, stock already committed to orders and stock ready to sell are different concepts. Shopify’s inventory documentation illustrates this distinction through inventory states. Your own system needs equally clear meanings, even if it uses another platform. Write them down for staff before configuring a website badge.
A branch may hold display units, damaged items or reserved stock. Another branch may have units that cannot be delivered today. Decide which locations fulfil online orders and whether transfers count as immediately available. If counts update periodically, make the customer promise fit that uncertainty rather than describing every number as live.
In practice · illustrative example
Follow one item through a branch transfer
Use a branch transfer as a practical design exercise. An item leaves one branch but has not yet been received at the other. Decide whether it is sellable during that interval and which staff member confirms receipt. If each branch simply edits its own total, your website may promise the same item twice or hide where it went.
Give the transfer a reference that staff can follow through dispatch, receipt and discrepancy handling. Rehearse a short delivery and a delayed connection. A reliable stock process needs visible exceptions, not only matching totals when everything succeeds. Keep product identity, movement and saleable availability distinct in the brief.
Stock in transit is a separate state
-
Request transfer
The branches agree the product identity and intended quantity.
-
Dispatch
The source records the movement against the transfer reference.
-
Receive
The destination confirms what actually arrived.
-
Resolve differences
Missing or extra quantities remain visible until staff resolve them.
Choose the moment an online order uses stock
Define what happens at checkout, payment success and staff acceptance. A temporary hold may need an expiry; a cancelled order may need to release its reservation. Decide how payment failures and repeated callbacks are handled so retries do not subtract inventory twice. These are business rules the developer needs before integrating.
For a busy product, test two customers attempting the last unit while the shop processes a sale. Agree which action wins and what the other customer sees. If a payment arrives after a reservation expired, staff need a documented resolution. Avoid silently creating negative stock and leaving the next shift to discover it.
Include transfers and returns in the same story
A transfer is not a sale. Record stock leaving one branch, travelling and arriving at another; decide when each location can promise it. Returns need inspection rules before an item becomes available again. Refunds, exchanges and inventory adjustments should remain understandable without assuming every financial event equals a stock movement.
Assign permissions for manual adjustments and require a reason your team can review. Use cycle counts or another agreed counting process to find discrepancies. When integrating existing software, ask for the exact supported interface and demonstration of the flows, not a general promise that “all systems can connect”.
Plan for the connection to fail sometimes
Agree what happens if a branch loses connectivity or an update is delayed. The system should expose failed exchanges and give staff a way to investigate them. Compare order references and movement records during reconciliation rather than overwriting counts blindly. Choose an escalation owner and a customer-facing fallback.
Pilot one branch and a small representative catalogue before extending the setup. Include variants, a bundle, a return, a cancellation and a transfer. Review errors with the employees who receive orders. A controlled rollout gives you evidence that the rules match daily work before the whole chain depends on them.
A worksheet for your team
Test movements as well as balances
Ask the branch and warehouse teams to use the same test item and inspect its movement history.
| Decision | Evidence to request | What to do next |
|---|---|---|
| Transfer identity | One reference linking dispatch and receipt. | Prevent unrelated manual edits from replacing the transfer record. |
| Short receipt | A transfer received with a different quantity. | Keep the difference visible and assign a resolver. |
| Connection delay | A branch temporarily unable to send its update. | Agree what the website can safely promise meanwhile. |
After the rehearsal, ask staff to explain the balance from the movement history. If they cannot, a matching final total may be hiding an unresolved process gap.
Before connecting your branches
- Stable product codes, variant mapping and unit definitions.
- An authoritative record and meanings for available and committed stock.
- Reservation, cancellation and return rules.
- Transfer records, adjustment permissions and physical-count checks.
- A failure queue, reconciliation owner and small pilot catalogue.
Frequently asked questions
Can every branch fulfil online orders?
Only if its availability, staffing and delivery process support that promise. Start with designated fulfilment locations and expand after testing the operation.
Is real-time stock always necessary?
It depends on sales volume and the cost of overselling. Describe update timing accurately and choose safeguards suited to the products and workflow.
Can I keep the public website static?
Information pages can remain static. Shared stock and orders require operational state; treat their integration as a separate system rather than storing live inventory in page copy.
Sources and further reading
These primary sources support the specific company or platform information in this guide. Provider descriptions do not imply an endorsement by the source.
Sources checked:
Review the movement of one product
Bring GateGold a sample product, your POS or inventory software details and the steps for a sale, transfer and return. Those examples help define a workable integration scope.
