Core Charges, MAP and Supersessions

Most margin advice assumes a simple world: one cost, one price, one product identity that stays put. The parts aftermarket breaks all three assumptions — with a deposit that isn't cost, a price floor you don't control, and part numbers that change identity underneath you. Each one quietly corrupts the numbers you make decisions on.

1. Core charges: a deposit wearing a price tag

Buy a remanufactured alternator, caliper, steering rack or A/C compressor and the invoice carries two amounts: the part and the core — a refundable deposit that comes back when the old unit is returned for remanufacturing. It's a loop, not a cost. It appears on your purchase invoice, on your customer's invoice, and on the credit memo when the core goes back.

Put $131.00 in Shopify's cost field against a $149.00 retail and the product shows a 12% margin. It's actually 42%. Multiply that error across every reman line in the catalog and your "which products make money" report becomes worse than useless — it's confidently wrong, and it points you away from a category that's often your best.

The mirror error is just as common: charging the customer a core but never accounting for the credit you receive back, so the revenue side is inflated instead.

How to handle it

• Keep the core out of cost per item. Cost is the part. Always.
• Sell the core as its own line — a separate product or variant, priced at the deposit, with cost equal to the deposit. Margin on it is zero by design, and that's correct: it's a pass-through, not a sale.
• Track core returns as an operational metric, not a margin one. Unreturned cores are a real loss, but they're a process problem (customers who never send the old unit back) and they belong in their own report — not smeared across product margins where they hide.
• Watch for cores in the price file. Core values change with the price file, and a core increase looks exactly like a cost increase to any diff that doesn't know the difference. Map the core column explicitly when you import, or you'll chase phantom increases every quarter.

2. MAP: a floor you don't control

Minimum advertised price policies are pervasive in performance and premium aftermarket brands. The brand sets the lowest price you may advertise — which for an online store effectively means the price on the page — and enforces it with warnings, then loss of the account.

MAP inverts the usual repricing logic. Elsewhere, a cost increase raises a question about what the market will bear. Under MAP the floor is fixed from above, which means:

• Raising prices is the easy direction. MAP constrains how low you go, not how high. If a cost increase pushes you under target margin, you can move up freely — the constraint isn't in your way.
• Your margin at MAP is a hard number worth monitoring. When cost rises and you're selling at MAP, your margin falls with nowhere to go but up in price — and at MAP, everyone visible is quoting the same price anyway, so a move away from it costs you the comparison you were winning.
• A cost increase can put MAP below your break-even. Rare, but it happens on thin lines. That's a conversation with the brand, not a pricing decision — and it's worth having early, because they generally do adjust MAP when their own costs move.

Worth noting: MAP governs the advertised price. Programs vary widely in what they permit around it — cart-price mechanisms, bundles, loyalty pricing — and the terms of your specific dealer agreement decide what's allowed. Read the policy rather than copying what a competitor appears to be doing; they may be about to lose the line.

3. Supersessions: when a product changes identity

Manufacturers replace part numbers routinely — a design revision, a consolidation, a supplier change. The old number is superseded by a new one, and the aftermarket carries the mapping so a counter person can find the current part from an obsolete number.

Your cost tracking, however, usually can't. Here's what a supersession looks like to a naive monthly diff:

A 30% increase entered the catalog as a brand-new product with no history to compare against. Nothing flagged it, because nothing knew the two rows were the same thing. And your Shopify product — still listed under the old number — now either can't be reordered or gets quietly relabelled by whoever notices first, taking whatever cost the new row carried.

How to handle it

• Keep a supersession map (old number → new number) and apply it before you diff price files, so the replacement lands on the existing product line. Most WDs publish this data; in PIES it comes through as interchange information.
• Treat a supersession as a price change on the same product, not as one item dying and another being born. That's the only way the history stays continuous — and history is the entire point.
• Keep the old number as an alias on your Shopify product (tags or a metafield). Customers search by the number printed on the box in their hand, which is frequently the superseded one.
• Check pack quantity on the new number. Consolidations often change packaging — a part that was sold each becoming a pack of two is a 100% "increase" that isn't one.

The pattern behind all three

Each of these is a case of the number in the file not meaning what a general-purpose tool assumes it means. A core is on the invoice but isn't cost. MAP is a price but not your decision. A new part number is a new row but not a new product. Generic inventory and profit tools, built for stores that sell mugs, treat all three at face value — and produce margins that are wrong in ways nobody notices, because nothing errors out.

That's also why the parts business rewards a proper routine more than most retail. The distortions don't announce themselves; they accumulate. A store that gets cores out of cost, watches margin at MAP, and maps supersessions before diffing is working from numbers that are simply true — which, over a catalog of tens of thousands of part numbers, turns out to be a bigger competitive advantage than any pricing strategy layered on top of bad data.