Requesting a tyre feed for WooCommerce: a practical checklist
Prepare a tyre feed or API request covering identifiers, prices, stock and update rules before connecting WooCommerce or another sales platform.
Contents
A useful tyre feed identifies the product, the offer with available stock and the price applicable to the trade account. Before requesting a TyreCenter integration for WooCommerce or another platform, prepare the commercial and technical details below. Format and access are defined for the agreed integration.
Information to include in your request
- Company name, tax ID and the B2B account email that identifies the pricing account.
- Your store address, platform and version, and a technical contact.
- Required tyre types, qualities and the sources or warehouses to include.
- Preferred format, required fields, refresh frequency and approximate catalogue size.
- Whether you need catalogue, price and stock only, or a separate order-submission workflow too.
A product code may not identify an offer
One SKU can have offers differing in source, quality, DOT or tread depth. Agree whether the import creates a product per SKU, variations or separate offer-level items. Update identifiers must remain stable so a changed price does not accidentally create another product or overwrite a different quality.
Agree the price and stock contract
Clarify price currency, VAT treatment, availability and any published-quantity limits. Your account’s purchase price is not automatically your resale price. Your own markup and store tax configuration are separate decisions.
Define what happens when a product disappears from a feed: sold out, withdrawn or excluded by the permitted sources. An incomplete download must not be treated as a valid instruction for bulk deletion. Refresh frequency is agreed for the integration; a feed does not reserve stock.
Test before publishing to your store
- 1
Start with a small sample
Compare identical SKUs and offers against the B2B account, including a new tyre and an offer with quality details.
- 2
Check updates
Confirm that price and quantity changes update an existing item instead of creating duplicates.
- 3
Test unavailable stock
Check missing-item rules and behaviour after incomplete responses or errors.
- 4
Protect access
Keep integration keys on the server, never in public pages, screenshots or browser-delivered code.
A CSV compatible with WooCommerce product import does not mean scheduled synchronisation, ordering or a plugin installation is already configured. Validate those separately before describing the integration as automatic.
Want your wholesale prices?
Open a B2B account and see real stock and your own discount grid on every product within minutes.
Frequently asked questions
Short answers to what partners ask us most often.
Does receiving a feed mean my store is already synchronised?
No. Importing, scheduling, error handling and missing-product rules must be configured and tested separately.
Can I use one SKU for every offer?
Only where the agreed data model allows it. Multiple offers under one SKU require identifiers that preserve the relevant differences.
Does a catalogue feed automatically send orders?
Do not assume that. Catalogue export and order submission are separate functions defined in the integration requirements.
