In this guide
If your online store sells products from a supplier, entering their stock and prices manually is manageable until the catalogue grows or availability changes frequently. A sync can help, but it needs rules that make the data trustworthy.
'Automated product updates' can mean several different things. One service may upload a CSV every week. Another may check an API repeatedly. A third may receive notifications when stock changes. The right arrangement depends on the supplier's actual capabilities and how quickly your store needs to react.
Start with a reliable product identifier
The most important field is usually a stable SKU or supplier reference. Names are not enough. A product may be renamed, described differently or sold in several colour and size combinations. The integration needs to know which incoming record matches which WooCommerce product or variation.
If two suppliers use the same code for unrelated items, a combined catalogue needs its own mapping rules.
Decide which source controls each field
A common mistake is treating the supplier as the source for every field. Suppose your team writes a useful product description and sets a selling price based on your costs. If the next supplier import overwrites both, the website loses local improvements.
A stronger approach separates the fields:
| Field | Possible source of truth |
|---|---|
| Supplier reference | Supplier feed |
| Supplier stock | Supplier feed, with local business rules |
| Supplier cost | Supplier feed |
| Selling price | Website pricing rules or approved local override |
| Public category description | Website content team |
| SEO title and copy | Website content team |
| Product photos | Supplier or approved local replacement |
The table is illustrative. The business must choose its actual rules before development.
What happens when the supplier feed fails?
Imagine a file normally containing 8,000 records suddenly contains 500. It might be a genuine reduction, or the export may have stopped early. If the website assumes all missing products have been discontinued, it could hide most of the catalogue.
A sensible sync may check expected row counts, duplicate IDs, blank prices, extreme changes and timestamps. Unexpected results can be held for review rather than applied immediately.
Updating stock, price and variations
Products with size or colour variations often need matching at variation level, not just at the parent product. Where a supplier has multiple warehouses, you need a rule for whether the displayed availability is a sum, a preferred location or a conservative stock amount.
Similarly, a supplier cost increase should not automatically create a negative margin. Margins, rounding, tax handling and minimum selling prices should be defined by the business.
How frequently should a store sync?
That depends on the external API, its limits and how quickly stock moves. Real-time stock is not possible if the supplier updates its own source only once a day. A reliable once-daily sync may be better than a fragile process that fails every few minutes.
Monitoring matters as much as frequency. Staff should be able to see the last successful run and any records that were skipped.
What should an integration report show?
At a minimum, useful logging might report when a job started and finished, records read, products created or updated, skipped records, failures and the last successful update. Sensitive credentials and unnecessary personal information should not appear in logs.
For a wider build, see supplier catalogue integration and WooCommerce API integration.
Questions to ask an integration developer
- Does the supplier offer an API, scheduled file or webhook?
- Can the system handle new, deleted and temporarily missing products separately?
- Are variations mapped by stable identifiers?
- Can we prevent selected content and prices from being overwritten?
- What happens if a sync partially fails?
- How do we test and reverse an incorrect mass update?
