Supplier feeds and price files

Open Integrations → Supplier price files→. You need the Edit settings permission.

Import a file

1. Pick the Supplier and drop their spreadsheet (.csv or .json).
2. Column mapping: tell BuildTrack what each column is: SKU (match key) (required), Product Name, RRP / Sell Price, Purchase Cost, Stock Qty (offsite), Supplier SKU, Image URL, Barcode, Brand, Category, Description, Vehicle Fitment Tags, Web Handle, and wheel and tyre specs. Known files map themselves (the Wheel Pros tech guide, a Shopify product export). A saved mapping is never replaced; the detected one is offered beside it.
3. What to update (all on by default except the Shopify image options and GST):

• Update RRP / sell price
• Update supplier purchase cost: updates the supplier link only, never your received cost history.
• Set offsite stock (snapshot): the supplier's stock, shown as plain in stock to dealers, franchises and your website without naming the supplier. Offsite stock can be sold and ordered, never picked.
• Create new SKUs: products not yet in your catalogue (they need a name and RRP).
• Update vehicle fitment (from tags)
• Only create wheels that fit my vehicles or bolt patterns
• Feed prices include GST (store ex-GST)
• Push image URLs to Shopify and Overwrite existing Shopify images

4. Product spec type: None, Wheels or Tyres. Wheels and tyres have their size, PCD and offset read out, even from the description.
5. Click Preview to see how many SKUs update, how many are new and what is skipped, then Import feed. Save mapping keeps the mapping without importing.

The first import saves the mapping as a Saved feed. Next time, pick it under Saved feeds (Use) and drop the new file.

Big files

The page only uploads the rows. The import runs on the server in batches, so you can close the tab once the upload finishes. Large files take a while: they work through a few hundred rows at a time and carry on by themselves, and an interrupted run resumes where it stopped. A row the catalogue won't take is listed and stepped over. Recent imports shows how far each run got, and Stop import stops one.

Mapping checks

Warnings appear above the column table before you import. No Product Name column with Create new SKUs on blocks the import (every new SKU would be skipped). A stock column that looks like a per-wheel count blocks until you tick that you've checked it. A brand column holding a code, or an MSRP column with GST off, gets a warning.

What a file won't overwrite

• Brands: a file fills a blank brand and never replaces yours. Distributor division names fold onto the brand (for example Fuel 1PC becomes Fuel Off-Road).
• Categories: a blank category is filled; an existing one is left alone.
• A stock cell with words instead of a number (In Stock, Low Stock, Out of Stock) is read as in, low or out. Prices written with "ex GST" or "AUD" are read correctly.

New products a file creates sit in the supplier catalogue, not your range, until you stock, order or sell them. See The product catalogue→.

Wheel feeds

• Vehicles you sell for: tick your models (each shows its bolt pattern) and Save vehicles. A wheel feed then creates only wheels that fit one of them. Products already in your catalogue are still updated whatever they fit.
• Bolt patterns you sell: add a pattern (8x170, or 8x6.5 in inches) or tick one from the loaded file, then Save bolt patterns. A new wheel is created when it fits a ticked vehicle or a chosen pattern.
• Nothing is filtered until at least one vehicle or bolt pattern is chosen.
• Wheel families groups single wheels into families (brand, style and finish, with the fitment as the variant). It runs after every wheel file; the button groups what is already there.

Daily email import

For a supplier who emails the file (for example a daily inventory feed is ready email with a download link):

1. Import the file once by hand so the feed and its mapping are saved.
2. Under Daily email import, pick the Feed, the Mailbox it arrives in (connect Gmail at Integrations → Gmail→ first), and fill From, Subject contains, Link text and, for a zip, the File inside the zip.
3. Save. BuildTrack checks every hour and imports a new email's file with the saved mapping. Check now runs one straight away. Each run shows under Recent imports; a failed check shows its reason on the card.

Product images

Integrations → Product images→ imports an image export keyed by Url handle. Handles are matched to each product's Web Handle, so map the Web Handle column on the price file first. Preview shows how many match, then Import images.

If something's not right

• New rows skipped: they need a product name and an RRP mapped.
• Wheels left out: they don't fit any ticked vehicle or bolt pattern. Preview counts them.
• "No matching email in the last 3 days": check the From and Subject on the email card.
• Import seems stuck: big runs pause between batches and pick up again within a few minutes. Watch Recent imports.