How to Organize Orders From Allegro, Your Online Store, and the Phone

It takes only three sales sources to turn a workday into window-hopping: an Allegro tab, your own store’s admin panel, an email inbox, and a sticky note with an order a customer dictated over the phone. Each source speaks a different language — different fields, different statuses, a different address format — and out of all of it you’re supposed to assemble one coherent list of “what are we packing today.”

This guide shows how to pull orders from a marketplace, your own store, and manual channels (phone, email, chat) into one queue, how to normalize the data so every order looks the same, and how to apply consistent statuses that actually tell you what’s going on. No theory — concrete steps and the usual traps.

Why three channels is more than three times the work

If every channel were a separate, sealed-off world, this would be simple. The problem is that channels overlap: the same product sells down on Allegro and in the store, the same customer writes once by email and once by phone, and you need to know how many parcels in total are waiting for the courier.

Typical symptoms of chaos with multiple sources:

• missed phone and email orders — because they have no “panel,” they live in someone’s head or on a sticky note,
• overselling — the last unit sold in parallel on Allegro and in the store,
• mismatched statuses — “processing” on Allegro means something different than in your store,
• no single packing list — staff don’t know where to start because they can’t see the whole picture.

The fix isn’t “more discipline,” it’s moving the truth about orders out of individual channels into one shared place — an OMS (Order Management System). We covered the bigger picture in the post on multichannel e-commerce without the chaos.

Step 1: pull everything into one queue

The first goal is trivially easy to state and hard to maintain by hand: every order, regardless of source, must land in one list. Not in three tabs — in one queue that staff work through top to bottom.

For digital channels an integration does this: the system fetches orders automatically (polling every few minutes, or event-driven) and adds them to the shared queue. In Sellaro the ready modules today are PrestaShop, Sylius, and WooCommerce; Allegro, Amazon, and Shopify are on the roadmap and added on request within your plan — the rule is simple: a missing integration we add for free.

What matters most, though, is what happens with channels that have no API — phone, email, a conversation at a market stall. That’s step three, because it’s the most commonly skipped piece of the puzzle.

Step 2: normalize the data so every order looks the same

Gathering orders into one window is only half the job. The other half is normalization — bringing every order to a single, shared structure so staff don’t have to relearn “where’s the address here” every time. A normalized order always has the same fields:

• internal number (yours, consistent) plus the original channel number,
• source channel — you see at a glance where it came from,
• customer and shipping address in one format,
• line items identified by SKU, not by name,
• amounts (products, shipping, total) in one presentation currency,
• internal status — yours, not the channel’s.

The heart of normalization is the SKU — the same product and variant code across all channels. It’s the link the system uses to know that “size M shirt from Allegro” and “T-shirt, size M from the store” are the same physical unit. Without consistent SKUs, shared inventory and reports don’t line up. If you sell on Allegro and WooCommerce, start by cleaning up your codes — the post on Allegro and WooCommerce stock synchronization helps.

Step 3: handle “manual” orders from phone and email

This is the most underrated channel. Orders from phone, email, or chat have no panel of their own, so they’re easy to forget — yet a customer who called expects the same fulfillment as one from Allegro.

The rule is one: enter a manual order into the same queue as the rest, immediately upon taking it. Not on a sticky note, not in a separate spreadsheet — into the system, so that it:

• draws down the shared inventory (you won’t sell that unit a second time on Allegro),
• gets an internal number and a status, like every other order,
• flows into the same reports and exports (e.g., CSV for accounting),
• is visible to the whole team, not just the person who answered the phone.

In practice it looks like this: you take the call, immediately create a manual order with the customer’s details and SKU-based line items, and from that moment it lives exactly like an order from a digital channel. As a result, “how many parcels do we have today” is one number, not the sum of three separate lists plus whatever someone remembers.

Step 4: apply consistent statuses across all sources

Once orders are in one queue and share a structure, they need one status dictionary. Every channel names the stages differently — your staff need a single set to describe everything:

1. new — received, awaiting handling,
2. paid — payment confirmed,
3. processing — being picked/packed,
4. shipped — handed to the courier,
5. completed — delivered and closed,
6. plus cancelled and return off the main path.

Map each channel’s statuses onto this internal set and stick to it consistently. Manual orders go through the same path. The result: on one screen you see how many parcels await packing, you set priorities by actual state rather than by panel, and you catch “stuck” orders before the customer reminds you.

You can’t manage what you can’t see in one place. A shared queue and one status dictionary are the precondition for knowing what’s actually happening in your business at all.

Step 5: automate the repetitive moves

Once the data is tidy, you can stop clicking the same things by hand. Repetitive rules are described with the WHEN → IF → THEN pattern (when an event → if a condition → then an action):

• when a new order comes in from any source,
• if the value exceeds a threshold or it’s a manual order needing verification,
• then send a notification to the team, tag the order, and record the event in the log.

Sellaro has an automation engine running on domain events, with actions: email (SMTP) and SMS notifications, webhooks (HMAC-signed, with retries), and log entries. Webhooks let you connect Sellaro to a tool that doesn’t yet have a ready integration — your script receives the event instantly.

An honest caveat: store integrations are READ-ONLY — Sellaro reads data from channels but does not write back to the store (it doesn’t change orders, doesn’t create Allegro offers). Generating courier labels and issuing invoices are roadmap goals, not features available today — we say so plainly.

Frequently asked questions

How do I get a phone order into the system?

You enter it manually into the same queue as digital orders — with the customer’s details and SKU-based line items. From that point it draws down the shared inventory, gets an internal number and status, and flows into reports like any other. The key is doing it right away, not “later, on a sticky note.”

Do I need a ready Allegro integration to start?

No. Start with the channels that are ready (in Sellaro: PrestaShop, Sylius, WooCommerce) and with manual orders; Allegro is on the roadmap and added on request within your plan. You set up the shared queue, inventory, and statuses once — additional channels simply plug in.

How is normalization different from just exporting to Excel?

Excel gives a static snapshot you must update by hand, and it watches neither inventory nor statuses. Normalization in an OMS is a living data model: every order has the same structure, shared inventory, and a consistent status, and the system reacts to events. More in the post on the Allegro order management system.

Will Sellaro change an order’s status on Allegro?

No — integrations are READ-ONLY. Sellaro maintains your internal status and reacts on its own side (notifications, webhooks, log). Writing statuses back to the channel is a development direction we describe honestly as roadmap.

Summary

Order out of chaos across Allegro, your store, and the phone comes down to five steps: pull everything into one queue, normalize the data around consistent SKUs, deliberately handle manual channels (phone, email), apply consistent statuses across all sources, and automate the repetitive moves. The rest follows — one list, one inventory, one status dictionary.

Want to work out what it costs? Check the pricing — 0% commission on sales, all integrations included in your plan, and a missing one we add for free.