Map your supplier fields to your store

Field mapping tells Everstock which part of your supplier's feed holds each piece of product data: the SKU, the barcode, the quantity, the price. You set it up in the "Inventory endpoint & mapping" section of the Connect a supplier wizard, and you can change it later without recreating the connection.

How a mapping row works

Each row pairs one Supplier field with one Maps to target. Supplier field is a dot path into a single supplier record, for example stock.available or attributes.ean. A leading $. is optional, and a numbered position reaches into a list, for example stocks.0.quantity. Maps to is a menu of the fields your store understands. Use Add mapping to add a row and Remove to drop one.

If two rows point at the same target, the app notes "Duplicate mappings for the same field: the last row wins.", and the preview badges the winning row "Duplicate: last wins". Order matters, so delete the row you do not want rather than leaving both.

The eleven fields you can map

The targets are SKU, Barcode, Title, Quantity, Price (decimal), Currency, Image URL, Description (HTML), Vendor, Product type, and Tags (comma-separated).

When you configure a supplier by hand, the wizard pre-creates rows for six of these: SKU, Barcode, Title, Quantity, Price (decimal), and Currency. Each one starts as a guess that your supplier uses that same name, so check every row against your real feed before you save.

The remaining five (Image URL, Description (HTML), Vendor, Product type, and Tags) start with no row at all. You add them deliberately with Add mapping, and only when your feed actually carries that data.

Mapping a field is not the same as syncing it. Quantity and price reach a matched product only when Sync inventory and Sync price are on. Title, Description (HTML), Vendor, Product type, and Tags only change an existing product when the matching switch under Product fields (advanced) on the connection page is on, and every one of those starts off. Image URL and any supplier metafields are used only when Everstock creates a product that was missing from your store.

Point Everstock at the records

Above the rows, "Records path (optional)" says where the array of records sits in the response, with $.data.items as the example. Leave it empty when the response is already the array. If your feed is CSV, set Response format to CSV: those rows are read from the header line, so they need no records path. Every Supplier field path is then read relative to one record, not to the whole response.

Matching is fixed at barcode, then SKU

Everstock always matches a supplier record to your store by barcode first and by SKU second. There is no setting for this. In the preview table you will see " · matching key" beside SKU and Barcode, and " · required" beside Quantity.

A supplier record with neither a barcode nor a SKU cannot be tied to anything in your catalogue, so it is set aside for review instead of being written. It appears in that run's Per-record audit with the change "Unmatched" and the action "Review". Two supplier records that resolve to the same key are set aside the same way, as "Duplicate". Nothing is guessed and nothing is written in either case.

Check your mapping before you save

Click Test connection. It fetches a sample and dry-runs your mapping, and it writes nothing to your store or to your supplier. On success you get a toast reading "Fetched N sample records"; on failure you get a banner headed "Couldn't reach the supplier feed". After a good test, the field paths found in the sample appear as clickable buttons, and clicking one fills in a row for you.

The live mapping preview has five columns: Canonical field, Mapped from, Sample value, Normalized, and Status. Sample value is the raw value from the feed and Normalized is what Everstock made of it, so a price arrives as money and a quantity as a number. The Status badge reads "Mapped", "Not mapped", "No data in sample", "Not a number", or "Not a price". If the matching key or Quantity is missing, a banner headed "This mapping can't sync yet" tells you which.

Below that, a per-record preview shows SKU, Barcode, Title, Quantity, Price, and Issues for the first three records of the sample. A record flags "no matching key" or "quantity missing/invalid", and a clean one badges "No issues". Both previews update as you edit, with no need to test again.

Change the mapping later

Open the connection and use the Field mapping section. It has the same Supplier field and Maps to rows, and leaving a row's supplier field blank unmaps that field. Click Save mapping when you are done, then run Preview changes to see the effect before any real sync.

Need help? Visit the support page or email hello@usenormalize.com.