A paid order should become a pick, a stock change, and a shipping note without someone retyping it into three places. Inventory should follow that same order, not a count you update when you remember. The aim is a short, repeatable path from payment to parcel, with a person still deciding the cases that cost you money or trust.
Start from the channels you already sell on. That may be a marketplace, your own site, or both. Write down what happens today between "paid" and "handed to the carrier." Note every place a quantity is typed, and every message a buyer receives. You are looking for copying, not for a new shop design.
What is worth automating
Four chores pay for themselves because they happen on almost every order:
- Order processing. A paid order lands in one queue with the buyer name, the SKU, the quantity, the ship-to address, and the channel it came from. Unpaid checkouts stay out of that queue.
- Inventory sync. The available quantity for that SKU drops when the order is paid, and the new number is written back to every channel that sells it. One place owns the count. The others reflect it.
- Low-stock alerts. When the available quantity hits a number you chose, one person gets a message. The message names the SKU, the quantity left, and which channel last sold it.
- Shipping updates. When a tracking number exists, the buyer receives the wording you approved, and the order is marked shipped on the channel that can accept that update.
If a chore does not happen most days, leave it manual until it does. Automation is for the path you can describe without saying "it depends" in the middle of the sentence.
Pick one quantity
Selling the same item in more than one place fails when each place keeps its own number. Choose the shelf, the sheet, or the store admin you pack from as the source. Then make the SKU text match everywhere. If one channel calls it MUG-BLUE and another calls it "blue mug," nothing can keep those counts aligned.
Write down what "available" means before you connect anything:
- On the shelf, and not already promised to a paid order.
- Or on the shelf, minus paid orders, minus checkouts you still hold stock aside for.
Two people on the same team often mean different things by "in stock." The workflow can only follow the sentence you wrote.
Set it up in this order
- List every channel that can take an order, and the hours you pack.
- Export the SKUs you actually sell. Fix duplicates and blank codes before you map them.
- Decide the event that moves stock. Paid is the usual choice. A cancelled order puts the quantity back only after a person confirms the item is sellable again.
- Set a low-stock number per SKU, or one default for the catalogue if your quantities are similar. Start higher than you think, so the first alerts are early rather than late.
- Write the shipping message in your own words. Include the carrier name and the tracking number, and nothing else the first week.
- Run new orders as drafts for a few selling days. Compare the queue with what you would have packed by hand. Turn on the live stock write and the buyer message only after that comparison looks dull.
What stays with a person
Refunds, replacements, address changes after a label is bought, and any cancellation that returns money stay with you. So does a listing that is live on a channel you have not mapped. A low-stock alert is a prompt to reorder or to pause a listing. It should not, by itself, hide the product or change the price.
When two channels disagree, show both numbers and the time of the last paid order. Do not let the workflow pick a winner. A person says which quantity is real, and that quantity is written back.
A short weekly pass
Once a week, read three lists: orders the queue refused, SKUs whose channel counts did not match the source, and low-stock alerts you ignored. If ordinary orders are being refused, the rule is too tight. If a buyer was told an item had shipped and it had not, pause the shipping message until you can see where the tracking number came from.
The useful question is not whether the automation ran. It is whether the exceptions were the ones you wanted a person to see.
If you want this path set up on the channels you already sell on, send a request for e-commerce automation.
Related: AI customer support for online stores.
