Multi-Platform Pricing

One supplier file in. Four channel-ready files out.

Your website, Amazon, eBay, and POS each need their own price — and their own file format. PriceTool keeps the rules in one place and produces a ready-to-upload file for every platform on every run.

The shape of one run

One file in, four ready-to-upload files out.

A single Harken supplier update produces four channel-specific outputs in the same run — each with its own markup, format, and compliance checks applied.

Supplier file in
Harken_PriceList_2026Q2.xlsx
1,284 SKUs · MAP enforced
Website
shopify_prices.csv
Cost × 1.34 · MAP floor · round to .95
Shopify product feed
Amazon
amazon_inventory.tsv
Cost × 1.42 · Buy Box buffer · ASIN map
Amazon flat-file
eBay
ebay_listings.csv
Cost × 1.48 · fee adj. · MSRP ceiling
eBay File Exchange
POS
lightspeed_import.csv
Cost × 1.30 · counter rounding
Lightspeed Retail
The pain

The same SKU has four prices, three formats, and a different rule for every platform.

A single supplier update isn't one job — it's one job copied four times, each with its own rounding, fees, MAP floor, and column order. Most retailers do this in a stack of spreadsheets. By Sunday night, the website and Amazon don't agree.

SKU
Website
Amazon
In-store POS
HK-50.2STA Harken 50.2STA Self-Tailing Winch · Cost $1,420
$1,902.00 × 1.34 · MAP floor
$2,016.00 × 1.42 · Buy Box +$5
$1,846.00 × 1.30 · counter
LW-V4-WCH Lewmar V4 Windlass · Cost $2,180 · MAP $2,725
$2,725.00 × 1.34 → held at MAP
$2,895.00 × 1.42 · ASIN B07X4...
$2,725.00 × 1.30 → held at MAP
RNS-RF40-A Ronstan Series 40 Mainsheet Block · Cost $186
$249.95 × 1.34 · round to .95
$264.99 × 1.42 · fee buffer
$241.80 × 1.30 · counter

Excerpt from a real PriceTool run report. Three SKUs shown — the engine produced 1,284 of these, with MAP, MSRP, ASIN mapping, and rounding applied per channel, in a single pass.

How it works

Each platform gets its own rule book — written once, applied every run.

The rules live in the engine, not in a spreadsheet someone has to remember. When a supplier file lands, every channel runs in parallel against its own configuration.

Website · Shopify

Margin-led, presentation-ready

Your storefront is the brand-facing channel. Higher margin, cleaner price points, MAP enforced, MSRP visible as compare-at.

  • Markup: 34% standard, 28% on rigging
  • Round to .95 / .99 endings
  • MAP floor enforced (Harken, Lewmar)
  • compare_at_price = MSRP
  • Sale flag carried forward from overrides
Exports as shopify_prices.csv · 14 columns · UTF-8
Marketplaces · Amazon, eBay

Fee-aware, Buy Box conscious

Marketplace prices have to absorb referral fees and stay competitive in the Buy Box. Each marketplace has its own SKU map and its own format.

  • Markup: cost × 1.42 (Amazon), × 1.48 (eBay)
  • Referral fee adjustment by category
  • ASIN / item-ID map per supplier line
  • Min-price guard for repricer compatibility
  • MAP held; MSRP capped
Exports as amazon_inventory.tsv · ebay_listings.csv
In-store · POS

Counter-friendly, walk-in pricing

The shop counter is a different game — round numbers, contractor pricing, and a different cost basis where it matters. Same supplier file, different formula.

  • Markup: 30% standard, 22% pro account
  • Round to whole dollars at counter
  • MAP floor enforced (no walk-in workaround)
  • Inventory location flag preserved
  • Pro-account tier exported separately
Exports as lightspeed_import.csv · pro_tier.csv
Why this matters

Platforms aren't just different formats. They're different businesses.

If you sell the same price everywhere, you lose money on Amazon and leave money on the website. Per-platform rules aren't optional — they're how the catalog stays profitable.

Amazon takes 8–15% off the top

Referral fees on chandlery categories run 8–15%. If your Amazon price isn't fee-adjusted, every sale is a 10% margin haircut. The rule has to live in the price, not in your head.

MAP isn't suggested — it's contractual

Harken, Lewmar, Garmin, B&G — every major supplier audits MAP. One under-MAP listing on eBay can cost you the line. The floor needs to be enforced before a file ever leaves the engine.

Walk-in customers don't buy in cents

Counter pricing rounds to whole dollars. Pro accounts get a different tier. Neither of those rules belongs in a Shopify CSV — but both belong in your POS export.

Each platform speaks a different file

Shopify wants a 14-column CSV. Amazon wants a TSV with a flat-file header. Lightspeed wants its own column order. The rules and the formats both have to be right.

What you receive

One package per run. Every channel file ready to upload.

When a supplier update is processed, every channel file is generated, validated, and packaged together — alongside the run report and a delta summary. You upload, you don't reformat.

Website
shopify_prices.csv
1,284 rows · 14 cols · UTF-8
Amazon
amazon_inventory.tsv
1,182 rows · flat-file · ASIN-mapped
eBay
ebay_listings.csv
874 rows · File Exchange · fee-adj.
POS
lightspeed_import.csv
1,284 rows · counter-rounded

Plus: run report PDF, change-summary CSV (deltas vs. last run), and a held-at-MAP exception list. Files arrive in your inbox; the engine keeps a versioned copy.

Stop maintaining four spreadsheets

Configure the rules once. Run every channel forever.

The work of selling the same SKU on four platforms is real. The work of maintaining four spreadsheets that disagree shouldn't be.

Request a demo