Skip to content
GuidesPlaybookUpdated 2026-11-188 min read

How do you move product, price list and buyer records out of spreadsheets?

Kevin Yum · Founder, Pixell
Short answer

Split the sheets into four linked records: products keyed by SKU, prices keyed by SKU, tier and start date, buyers keyed by their tax ID, and terms per buyer with a start date. Merge duplicates on the tax ID, not the name. Test-import 20 rows, import the rest, then lock the old sheets so nobody keeps editing a second copy.

Checklist
  • A list of every sheet, its editors and what depends on it
  • One key per record: SKU, buyer tax ID
  • Price rows with tier, start date and end date
  • Buyer terms with a start date
  • Aliases kept for every merged duplicate
  • A 20-row test import
  • Old sheets protected after the switch
  • One owner per record type

A wholesale brand's spreadsheets usually start as one product list and one buyer list. A year later there is a price sheet per season, a copy per salesperson and a tab of special deals nobody remembers agreeing to. Moving out is less about choosing software and more about deciding what the keys and dates are.

A laptop showing charts next to a tablet with a spreadsheet

When is a spreadsheet still fine?

Check whether you need to move at all. A spreadsheet is enough while the three answers below are all yes, and you can still say what price a buyer got in March without asking anyone.

Is a spreadsheet still enough for you?
Does only one person edit prices and terms?
No
Move to keyed records

Two editors, two truths

Yes
Is every buyer on one price list?
No
Move to keyed records

Exceptions outgrow one column

Yes
Are orders and invoices typed by hand?
Yes
A spreadsheet is fine
No
Move to keyed records

When any answer turns to no, the cost shows up as errors: a buyer invoiced at an old price, an order shipped to a closed store, or one buyer entered twice with different terms.

What the spreadsheet looks like by then
A statement spreadsheet named statement_final_v2 (3).xlsx with a #REF! error and a question-marked quantity, beside a purchase order email

What fields should each record keep?

Each record needs one key that never changes, plus the fields orders and invoices read from it.

Four records, one key each
Key: SKU
Product
NameBarcode (GTIN)Unit sizeCase packActive or discontinued
Renaming never changes the SKU
Key: SKU + tier + start date
Price
PriceCurrencyMinimum quantityEnd date
Added with dates, never overwritten
Key: tax ID of the legal entity
Buyer
Legal nameTrading nameAliasesBilling addressShip-to locationsContactsInvoice emailStatus
Name and tax ID as registered
Key: buyer + start date
Terms
Price tierPayment termsCredit limitMinimum orderBuyer-specific prices
A change is a new row

Splitting terms from the buyer is the step most teams skip. Without it, changing a buyer's payment terms silently rewrites the history of every earlier order.

A buyer record with its terms kept apart
A sample buyer record for Harbor & Pine Beauty with tier T2, prepaid payment terms, monthly invoicing, a ship-to store and three contacts
One buyer record, keyed by tax ID
Buyer record
1Tax ID
As registered, never changes
Legal name
Greenleaf Pharmacy LLC
2Aliases
Greenleaf Pharmacy · GreenLeaf - Main St
Ship-to locations
One per store
3Terms
Tier B, from a start date
  1. 1Merge on this, not the name
  2. 2Old spellings still match orders
  3. 3A term change is a new row

How do you structure price tiers and buyer-specific prices?

Use one list price per SKU, a few tiers, and buyer-specific prices only as exceptions. Decide the order of precedence once and write it down.

Which price applies on the order date?
  1. 01
    Buyer-specific price

    If active that day

  2. 02
    Buyer's tier price

    Otherwise

  3. 03
    List price

    If neither exists

One price per product and tier
A sample product list of four products, each with T1, T2 and T3 tier prices from the price list
Rice toner 150 ml · TONER-150
List price
$14.00
From 2026-01-01
Tier A · distributors
$8.40
From 2026-01-01
Tier B · independent stores
$9.80
From 2026-01-01
Greenleaf Pharmacy (Tier B)
$9.20
Agreed, 2026-12-01 to 2027-05-31
Greenleaf's toner price, by order date
  1. 2026-01-01

    Tier B $9.80 starts

  2. 2026-11-20

    Order billed $9.80

  3. 2026-12-01

    Agreed $9.20 starts

  4. 2026-12-03

    Order billed $9.20

  5. 2027-05-31

    Back to tier price

Without the dates, the sheet can only show today's deal, and every past invoice becomes hard to check.

15%, 10% and 10% off is not 35%
Adding the percentages
35%
What the buyer actually saves
1 − 0.85 × 0.90 × 0.90
31.15%
Stacked discounts compound

A tier discount, a volume break and a promotion multiply rather than add. Store the final net price per tier when you can, rather than a chain of percentages.

How do you find and merge duplicate buyers?

Duplicates come from typing, not bad intent. "Greenleaf Pharmacy", "Greenleaf Pharmacy LLC" and "GreenLeaf - Main St" are often one buyer entered by three people.

Merge these two buyers or not?
Do both rows have a tax ID?
No
Review by hand, ask for the tax ID
Yes
Is it the same tax ID?
No
Separate buyers, linked as a group

Franchisees, for example

Yes
Are the addresses different?
Yes
One buyer, several ship-to locations
No
Merge, keep old names as aliases

Match on the tax ID first. For rows without one, compare a cleaned name (lower case, no punctuation, "LLC" or "Inc.") with the postcode or email domain, and review every proposed merge yourself.

Products get the same treatment. Two rows with one barcode are one SKU, and a set lists its component SKUs rather than becoming an unrelated product.

How do you move the data in seven steps?

  1. List every sheet
    Each file and tab, who edits it, and what is built from it: order forms, invoices, the price list you email buyers.
  2. Choose the keys
    SKU for products, tax ID for buyers. Rows without a key go on a fix-first list.
  3. Clean in a copy
    Split buyer terms and prices out of the buyer list into their own tables with start dates.
  4. Merge duplicates
    Apply the rules above and keep every old spelling as an alias.
  5. Test-import 20 rows
    Open each record and check that prices, terms and contacts landed in the right fields.
  6. Import the rest, run one cycle in parallel
    Take orders and invoice from the new records for one billing cycle, with the old sheets there to compare.
  7. Lock the old sheets, name owners
    Protect the old sheets so edits are blocked or warned, and give each record type one owner who approves changes.
A test import: the file, then its columns
A sample price list spreadsheet dropped in for import, previewing four products with three price columns and a notes column
Column matching for the price list: four of five columns matched, with Store price to T1 price flagged for a check

What usually goes wrong?

  • Importing before choosing keys. Buyers matched on names drift apart again within weeks.
  • Overwriting prices. The new system shows only today's deal, just like the sheet.
  • Merging franchisees. Two stores, one brand name, two tax IDs: one invoice, and both reject it.
  • Leaving the old sheets open. Someone keeps editing the old file and you have two truths again.
  • Cleaning everything first. Fix keys and duplicates, then import. Missing phone numbers can wait.

Where Pixell fits

Two people working on laptops, one writing on a notepad

Once these records are clean, the work on top of them repeats every week: checking orders against the price list, keeping buyer terms current and closing the month with each buyer. Pixell Agent can run that work inside the rules you set, and bring you only the exceptions.

Questions

When is a spreadsheet still fine?

When one person edits it, you have a handful of buyers on one price list, and no order or invoice is built from it automatically. Once two people edit prices or terms, or invoices depend on the sheet, you need records with keys and dates.

Do I need an ERP to manage wholesale buyers?

Usually not at first. A small brand needs clean products, prices, buyers and terms that orders and invoices read from. An ERP adds accounting, purchasing and stock, which you can connect later to the same keys.

How do I handle a buyer with several stores?

Keep one buyer record for the legal entity, keyed by its tax ID, and add each store as a ship-to location. If each store is its own legal entity with its own tax ID, they are separate buyers in a group.

How should I store price changes?

Never overwrite a price. Add a new row with a start date and close the old one with an end date. Then you can always answer which price applied to an order on a given day.

What is the safest way to dedupe a customer list?

Match on the tax ID first, then on a normalised name plus postcode, and review the uncertain pairs by hand. Keep every old spelling as an alias so incoming orders still match.

Tell us what you'd hand off first

Thirty minutes. We map it to rules and show you what Pixell Agent would own.

Book an operations review

Related guides