How to Run a Single Inventory for Allegro and WooCommerce Sales
You sell on Allegro and in your WooCommerce store from the same shelf. The same box, the same units, just two channels that know nothing about each other. The question that decides how smoothly your operation runs is this: do you run one inventory for both channels, or two separate ones that you try to reconcile by hand?
This guide isn’t about stock synchronization itself — we cover that separately. Here it’s about organization and processes: how to set up one inventory that serves Allegro and WooCommerce at once, what rules to put in place, and how that differs from running two warehouses side by side.
One logical inventory, two sales channels
First, separate two concepts that sellers often confuse:
- Physical warehouse — the shelf, the box, the actual units you touch while packing.
- Logical inventory — the record in your system that says how many units you have and how many are available to sell.
Physically you have one warehouse anyway — you ship both the Allegro order and the store order from the same shelf. The trouble starts when you run two logically: one stock figure typed into Allegro and another into WooCommerce. Now two numbers describe the same box, and sooner or later they drift apart.
There is one rule for running multichannel inventory: one logical inventory (one true unit count), and the channels merely reflect it. Allegro and WooCommerce stop owning the stock — they become views of it. We break down the foundations of this minimal inventory in our piece on what a simple warehouse system for an online store must have.
SKU as the backbone of the whole inventory
Everything else rests on one thing: consistent SKUs. The SKU is the code by which the system recognizes that an Allegro offer and a WooCommerce product are the same physical unit. Without it you don’t have one inventory — you have two catalogs that happen to sell the same thing.
When you run inventory for both channels, stick to a few rules:
- One SKU per physical item — assigned once, when you create the product, not when you list an offer.
- The same SKU on both sides — in the Allegro offer signature and in the WooCommerce product SKU field.
- A convention, not improvisation — set a code scheme (e.g. category-model-variant) and stick to it, so a new product drops into the system without guesswork.
Clean SKUs are the most boring and the most important part of running inventory. Invest in them up front, and every later decision — reservations, variants, alerts — will simply work.
Variants: count stock at the size level, not the product
If you sell anything in sizes, colors or capacities, the stock unit is the variant, not the product. It sounds obvious, yet it’s the source of most multichannel mistakes.
The classic error: a “T-shirt” product has a combined stock of 10 units, and both Allegro and WooCommerce show it as available even though size M has been gone for a week. The customer orders an M that isn’t there — cancellation and refund.
So when running inventory for both channels, set:
- each variant = a separate item with its own SKU and its own stock,
- one-to-one variant mapping — size M on Allegro is the same row as size M in WooCommerce,
- a stock view per variant, not just the product total.
This is the most common difference between an inventory that “roughly matches” and one you can actually rely on.
Reservations: stock drops at order time, not at shipping
The most important process rule in multichannel inventory: a unit is reserved the moment the order is placed, not when you pack the parcel. This closes the most dangerous window — the time between a sale on one channel and its shipment, during which the other channel still shows the item as available.
A practical stock formula worth using:
Available = on hand − reserved − safety buffer.
When a customer buys on Allegro, the unit immediately leaves the pool available to WooCommerce — even if the parcel ships tomorrow. On top of that it’s worth keeping a small safety buffer (a few units held back) to absorb sync delays and returns in progress. Reservations and the buffer are exactly what separate running one inventory from nervously watching two. For the actual flow of numbers between channels, see our guide to stock synchronization between Allegro and WooCommerce.
Day-to-day processes: receiving, picking, returns
One logical inventory works only when every stock change passes through the same place. That’s a matter of process discipline, not technology:
- Receiving a delivery — you record a new batch once, into central stock. Not “in Allegro” and separately “in the store,” but into one figure that then spreads to the channels.
- Picking and packing — you pick from one shelf regardless of which channel the order came from. It helps to unify labeling and the staging area, so the packer doesn’t have to guess whose order it is.
- Returns — the unit goes back into the shared pool and becomes available to both channels again. An Allegro return can’t feed only an “Allegro warehouse,” because no such warehouse exists.
- Corrections and stocktakes — you post adjustments to central stock, not separately per channel.
It comes down to one rule: one source of truth, one place for changes. Channels read, they don’t write.
One inventory vs two separate ones — the difference
Why bother with a single inventory at all, when Allegro and WooCommerce each have their own stock counter? Because two separate warehouses carry a cost that grows with scale:
| Aspect | Two separate warehouses | One logical inventory | | — | — | — | | Stock | Two numbers for the same goods | One true unit count | | Overselling | Constant risk on the last units | Reservation closes the window | | New product | Entered separately in each channel | Once, spreads to the channels | | Returns | You must remember where to restock | Go back into a shared pool | | New channel | Another warehouse to watch | Another view of the same stock |
Two warehouses look tempting at the start because “you’ll keep an eye on it somehow.” The problem is that the cost of keeping an eye on it grows with every product, variant and channel — until at peak sales it turns into cancellations and negative ratings.
Where Sellaro fits in
Sellaro is an OMS (order and product management system) that gives you that single logical inventory: products and variants from all connected channels land in one shared view, split into available, low and out-of-stock, tied together by SKU. Store integrations (PrestaShop, Sylius, WooCommerce) work read-only — Sellaro reads and normalizes data, it does not write back to the store. The Allegro integration is on the roadmap and we add it on request within your plan; any missing integration we add for free.
Low-stock alerts and return notifications you set up as a rule in the automation engine (WHEN→IF→THEN) with an email (SMTP) or SMS action. The platform is under active development — we write about this honestly, so you know what works today and what we’re still adding.
Frequently asked questions
Do I really need one inventory if I ship from a single shelf?
Physically you already have one warehouse — the problem is logical. If you keep stock separately in Allegro and in WooCommerce, two numbers describe the same box and they’ll eventually drift apart. One logical inventory means one true unit count, with the channels merely displaying it.
Where do I start organizing inventory for two channels?
With SKUs. Give every product and variant a unique, consistent code and enter the same SKU on both sides — in the Allegro offer signature and in the WooCommerce product field. It’s the backbone the rest depends on: reservations, variants and shared stock.
How do I keep stock for size variants?
Count stock at the variant level, not the product level. Each size or color is a separate item with its own SKU and its own stock, mapped one-to-one between Allegro and WooCommerce. Otherwise a product shows as available when the specific size is already gone.
How do I handle returns with a single inventory?
The returned unit goes back into the shared pool and becomes available to both channels again — regardless of which channel the order came from. The key is to post the correction to central stock, not separately “in Allegro” or “in the store.”
Summary
Running inventory for Allegro and WooCommerce is above all about organization, not technology. Keep one logical inventory with consistent SKUs, count variants at the right level, reserve the unit at order time, and make sure every change — receiving, returns, corrections — passes through one place. Two separate warehouses seem simpler at the start, but their cost grows with every product and channel.
Want to run one inventory across all your channels? Start with the basics of a simple warehouse system, see how Allegro and WooCommerce stock synchronization works, and calculate your cost in Sellaro. Any missing integration we’ll add free within your plan.