Key takeaways
- The work does not scale linearly. Each new client adds its own suppliers, margins and failure modes.
- One feed per client per supplier. Sharing feeds couples clients together and widens every outage.
- Standardise three things: SKU format, category naming, markup rules. Let everything else differ.
- Automate stock first, then price, then new products. That is the order of how much the failure hurts.
The first client store is a workflow. You know the supplier, you know the margins, you notice when something looks wrong.
The fourth is an operations problem. Four suppliers change prices on four different schedules, each store has its own markup, and you no longer notice anything until a customer does.
What actually breaks as you add stores
It is rarely the thing people expect. Volume is fine; computers handle rows. What degrades is attention.
| Stores | What it feels like | What is actually failing |
|---|---|---|
| 1 | Manageable | Nothing. You see everything. |
| 2 to 3 | Busy but fine | You start batching checks, so problems live longer. |
| 4 to 6 | Always behind | You only find issues when a client reports them. |
| 7+ | Firefighting | You no longer know which stores are currently correct. |
The turning point is when you stop discovering problems and start being told about them. Everything below is aimed at pushing that point further out.
Give every client their own feed
The tempting shortcut when two clients use the same supplier is to share one connection. Do not.
Shared feeds couple clients:
- A markup change for one becomes a markup change for both.
- A supplier outage takes every store using it down together, at the same moment, in front of every client at once.
- You cannot pause, re-sync or debug one client without touching the others.
- When something looks wrong, you cannot tell which store is affected without checking all of them.
One feed per client per supplier costs nothing extra in effort and keeps the blast radius the size of one client. It also means a client asking "why did my prices change" has a single, answerable trail.
Name feeds for the client, not the supplier. northbound-tools beats bikerswarehouse when you have three clients pulling from the same source and a client emails you at 5pm.
Standardise exactly three things
The instinct is to make every client identical. That fails, because clients have genuinely different businesses. Standardise the three things that let you move between stores without relearning each one, and let everything else vary.
1. SKU format
This is the important one. Every sync matches on SKU, so a consistent format is what makes re-syncing safe across every store you run. Pick a shape, apply it everywhere, and never reuse a retired SKU.
2. Category naming
Not the same categories, the same conventions: same separator, same capitalisation, same singular or plural. Inconsistent spacing around a separator silently creates duplicate taxonomy terms, and doing that across ten stores is a long afternoon.
3. Markup and rounding rules
Different clients can take different margins. What should not differ is how the rule is expressed. "60 percent, round to .99" applied identically everywhere means you can reason about any store's pricing without opening it.
Twenty five feeds, one account
The Agency plan runs 25 synced supplier feeds, so every client keeps its own source, markup and schedule without sharing anything with another client.
Automate in order of pain
You cannot automate everything at once, so do it in the order of how badly each failure hurts.
- Stock. Selling something a supplier no longer has produces a refund, an apology and a review you cannot remove. Enough of it and the client's payment processor starts asking questions. Fix this first, always.
- Price. Drift here costs margin quietly. Painful, but it does not damage the client's reputation.
- New products. Missing them costs opportunity, not money you already had.
- Descriptions and imagery. Worth human attention on the lines that get advertised, and worth leaving alone otherwise.
The general mechanics of keeping a catalogue current are in how to keep a WooCommerce store in sync with your supplier. Everything there applies per client; this piece is about what changes when there are many.
Build one place that tells you the truth
The failure mode at scale is not knowing which stores are currently correct. You need one view answering:
- When did each feed last sync successfully?
- Which ones are failing, and for how long?
- Which client does each belong to?
Without that you are reduced to opening stores and looking, which is exactly the manual attention that stopped scaling at store four.
A silently stale feed is worse than a broken one. A feed that fails loudly gets fixed. A feed that keeps serving its last good snapshot looks healthy while quietly handing a client month-old prices and stock. Check the last successful sync time, not just whether the feed responds.
What to tell clients
Two things, in writing, at the start:
What is automated and what is not. Prices and stock update hourly. Product descriptions do not rewrite themselves. Clients assume "automatic" means everything, and the gap becomes your problem at the worst moment.
What happens when a supplier breaks. Suppliers redesign sites, add bot protection, go under. Say in advance what you will do, and how quickly you will tell them. A client who was warned treats it as a supplier problem. A client who was not treats it as your failure.
Charge for the ongoing part
A common mistake is charging a setup fee and then absorbing the maintenance. Setup is a day. Maintenance is forever, and it is the part that scales badly with client count.
Price the ongoing sync as a retainer. It reflects the real cost, it makes you willing to invest in automation, and it means the fourth client makes you money instead of costing you evenings.