Omnichannel inventory management runs all your branches and sales channels from one stock record, so any of them can sell any unit you hold. It works when each channel shows what it can deliver, not the total you own.
This guide sets out the four services it makes possible and works out what a Lagos retailer's website should show. It ends with five steps and how to run them in ArmPOS.
Omnichannel vs multichannel inventory: one pool or several
Multichannel means selling in several places, each with its own stock; omnichannel means one pool that every channel draws on. The difference shows when a customer wants an item that sits in another branch.
| Question | Multichannel | Omnichannel |
|---|---|---|
| How many stock records? | One per branch or channel | One for the business, split by location |
| A customer wants an item another branch holds | "We don't have it" | Hold it there, or move it to them |
| Who fills an online order? | One fixed store room | The location that can deliver it soonest |
| Where do returns go? | Back to the channel that sold them | Taken anywhere, then moved to where they sell |
| What does it need? | Little | One product list, one code per item and a rule for each order |
Most small retailers become multichannel without choosing it. It happens the day a second branch opens with its own exercise book, or a website starts its own stock count.
Running the branches themselves, their cash, staff and weekly figures, is multi-location retail management. This page is about the stock they share.
The four omnichannel services, and what each needs from your stock
Omnichannel retail rests on four services: click and collect, ship from store, selling from another branch, and returns taken anywhere. Each needs one thing from your stock records, and each fails in a known way.
| Service | What the customer gets | What the stock record must show | How it fails | Offer it when |
|---|---|---|---|---|
| Click and collect | Buys online, collects at a branch | That branch's stock, with the unit held for the order | The counter sells the held unit to a walk-in | Customers already phone to ask if you have it |
| Ship from store | Delivery from the nearest branch | Each branch's own stock, beside the total | Two branches ship the same order, or none does | Your branches are in different parts of town |
| Selling from another branch | The counter sells what another branch holds | Every branch's stock, visible at the till | The goods never move and the customer waits | Branches carry different ranges |
| Returns taken anywhere | Brings an online buy back to any branch | Where the returned unit sits now | The records place it in one branch while it sits in another | You sell online to more than one town |
Start with one service on your best-selling lines, then add the next. Each service is also a delivery choice, compared on cost in order fulfillment strategies.
How much stock should each channel show? A worked example
Each channel should show what it can hand over within its promise: stock on hand, less orders already accepted, less a small buffer. Showing every unit you own invites orders you can't fill in time.
Available to promise = stock on hand − orders accepted but not yet taken from stock − buffer
For example, a homeware retailer in Lagos has branches in Ikeja and Lekki, and its website ships from Ikeja. It sells a blender at NGN 45,000. The figures are illustrative.
| Location | On hand | Orders accepted, not yet taken from stock | Buffer | Available to promise |
|---|---|---|---|---|
| Ikeja (also ships the website's orders) | 14 | 3 | 2 | 9 |
| Lekki | 6 | 1 | 2 | 3 |
| Both branches | 20 | 4 | 4 | 12 |
A website fed with both branches' total shows 20 blenders, 8 more than the business can promise. That is NGN 360,000 of orders it may have to delay or refund.
A website fed with Ikeja alone shows 14, still 5 more than Ikeja can promise. Three orders wait unconfirmed, and nothing keeps the buffer.
Common advice says to show customers every unit you own. For a retailer whose branches sit an hour of traffic apart, that promises goods you can't move in time.
Two habits close most of the gap. Confirm orders quickly, so they leave the count, and feed the website from the branch that ships its orders.
How to build omnichannel inventory management in five steps
Five steps turn separate counts into one stock. First write down where stock lives today and who updates each figure, because every step below replaces one of those habits.
1. One product list, one code per item
Every item needs one code, used by every branch, the till and the website. GS1's GTIN, the standard behind retail barcodes, exists so a company can "uniquely identify all of its trade items".
Two codes for one blender mean two stock figures, and one of them is always wrong.
2. One location for each place stock sits
Give each branch and store room its own location in the system, with its racks and shelves. A total without locations can't tell a customer where to collect.
3. Decide which location serves each channel
Feed the website from the branch that packs online orders, and say so in your routine. A branch that serves the website keeps its buffer for it.
4. A rule for moving stock
Move stock between branches only with a record that someone approves, and move returns back to where they sell. This is where inventory management and warehouse management meet: the record and the goods must travel together.
5. A daily routine, and counts by location
Each morning, confirm waiting orders, read the low stock list for each branch and move what is short. Count each branch on a rota, one section a week.
Train each branch on the same routine, and give each person the branches they work in. A rule only one branch follows makes the shared count wrong for all of them.
How to run omnichannel inventory in ArmPOS
ArmPOS treats each branch as a warehouse with its own stock, in one account with one product list. These are the steps, each with its Help center guide.
- Add a warehouse for each branch, and its racks and shelves as locations: Your warehouse and its locations. Your plan sets how many warehouses you can have (pricing).
- Point the online store at the branch that ships. Online orders take stock from the store's Default Warehouse, set in Store › Settings: Set up your online store.
- Confirm to hold the stock. A pending order takes nothing; Confirm turns it into a sale and takes the stock, so the counter can't sell that unit: Online orders.
- Tell the customer yourself. ArmPOS doesn't email on confirm, and its store offers no delivery options at checkout, so call or message to arrange collection.
- Choose what other websites see. WooCommerce's Sync stock now sends all warehouses added up; a Shopify store can be tied to one warehouse: WooCommerce and Shopify. Both guides were written from the screens and code, not run against a real shop.
- Move stock with approved transfers. Sent takes stock out of one branch while it travels; editing it to Completed puts it into the other: Move stock between warehouses.
- Follow returns with a transfer. A return goes back into the warehouse the sale came from. If the goods land at another branch, transfer them so the record follows: Returns and refunds.
- Limit each person to their branches under Access warehouses: Roles and permissions.
- Watch stock by branch. Low stock alerts go to the people at that warehouse. Most stock reports narrow to one warehouse: Get alerts on your phone and Stock reports.
The online store, transfers and the WooCommerce and Shopify links come with some plans only. ArmPOS runs this way for retailers in Nigeria and every other country it serves.
Frequently asked questions
What is the difference between omnichannel and multichannel inventory?
Multichannel keeps a separate stock for each channel or branch. Omnichannel keeps one record, split by location, that every channel can sell from.
What is click and collect?
The customer buys online and collects at a branch. It works when that branch holds the unit for the order the moment it is accepted.
What is ship from store?
Delivering an online order from a branch rather than a central store room. It needs each branch's own stock figure, not just the total.
Does a small retailer need an order management system?
Not to start. One stock record by location, a rule for which branch fills each order and a daily routine cover two or three branches.
Will AI forecasting fix omnichannel stock?
Only once the records are right. AI tools forecast from your stock and sales history, so a wrong count by branch gives a wrong forecast by branch.
Pick your best-selling line this week and write down its stock, accepted orders and buffer at each branch. Then create a free ArmPOS account, add each branch as a warehouse when your plan allows, and run every channel from one count.
