Your supplier emails a price list. It is a CSV with their column names, their number formatting and their product codes. Somewhere between that file and your storefront, somebody has to work out which of their rows is which of your variants, add your margin, round to something sellable, and type it all in.

Most stores do this by hand, quarterly, and dread it. Some do it with a VLOOKUP they rebuilt three times. This guide covers doing it as a repeatable import: map the supplier's file once, set your pricing rules, and run it whenever a new file arrives.

Why a supplier feed is harder than a normal import

A SheetSync sheet is a mirror of your store, so its columns are known. A supplier feed is somebody else's document, and three things about it are unpredictable:

Handling those three things is the whole job.

Reading the file

SheetSync accepts the feed as a URL — a download link, an FTP-style endpoint, or a supplier API — and works out its shape rather than asking you to describe it.

The delimiter is detected, not assumed. Commas, semicolons, tabs and pipes are all common; European exports use semicolons precisely because their decimal separator is a comma. The detection reads the first several lines and picks the delimiter that yields a consistent column count, counting only outside quoted fields — otherwise a description column full of commas wins every time.

Number format is decided per column, not per cell. Every sampled value in a column votes on whether it looks European or Anglo, and the column is read that way throughout. Deciding per cell is how 1.234 becomes 1.234 in one row and 1,234 in the next.

Currency symbols and codes are noise. €24,90, 24.90 EUR and 24.90 all read as the same number.

Matching their rows to your variants

This is where imports usually go wrong, so it is worth being precise about how it works.

Matching is an exact join on SKU or barcode — a hash lookup, not a fuzzy guess. Nothing approximate ever matches, because a nearly-right match silently reprices the wrong product, which is worse than not matching at all.

Two details make that practical:

Barcodes identify themselves. A GTIN carries its own check digit, so a column where most values validate is the barcode column whatever the supplier titled it. That is a far stronger signal than any header text.

Ambiguous identifiers are refused, not resolved. If a SKU appears on two of your variants, it identifies neither — both are excluded from matching and reported. Picking one would reprice a product at random.

Where the supplier's codes nearly match yours, a small transform bridges the gap without editing the file: strip a prefix or suffix, remove a character, or uppercase. If their ACME-TS-001 is your TS-001, stripping ACME- is the whole fix.

Turning their number into your price

Markup rules run on the matched value, and they are explicit about something merchants mix up constantly: markup and margin are not the same thing.

Then rounding, because 13.3042 is not a price:

The preview shows the working rather than just the answer: 9.50 from the feed → +40% markup → 13.30 → rounded up to .99 → 13.99. A decimal point in the wrong place is obvious in that line and invisible in a column of finished prices.

Step by step

  1. On the Pricing page, choose Import prices from a supplier.
  2. Give the feed's URL and, if it needs one, its credential — basic auth, a bearer token, a custom header, or a key in the query string.
  3. SheetSync inspects the file and proposes a mapping: which column is the identifier, which is the price. It tells you when it is unsure rather than guessing silently.
  4. Confirm the mapping and add an identifier transform if their codes are prefixed.
  5. Set your markup and rounding rules.
  6. Review the preview: matched, unmatched, ambiguous, and the exact price for each row.
  7. Approve. The changes run through the same pipeline as every other sync, so they appear in Activity with full undo.
  8. Save the feed. Next time the supplier sends an update, it is one click.

Credentials are encrypted, not stored in the clear

A saved feed usually needs a password or an API key so it can be re-fetched without you retyping it. That is a real secret belonging to a third party, so it is encrypted at rest with AES-256-GCM, using a key the database does not contain — a dump of the table yields ciphertext and nothing else. Credentials are never echoed back or written to logs; a request that carries one is redacted before it is recorded.

If no encryption key is configured on the server, storing a credential is refused rather than falling back to plaintext. A silent downgrade is the worst possible outcome, because it looks like it worked.

Practical notes

Who this is for

Stores that resell: distributors, dropshippers, trade suppliers, anyone whose cost prices come from somebody else's spreadsheet on a schedule. If repricing is currently a quarterly day of work you keep postponing, this is the thing that turns it into a five-minute review.

The same mechanism handles stock — see updating Shopify stock from a supplier feed.

Let your supplier's file do the work

Point SheetSync at a supplier feed, set your markup rules, and preview every price before it lands.

Try SheetSync today
← Bulk update Shopify pricing