De Minimis Is Dead: Importing a $15 Product Now Needs New Landed-Cost Math

A $15 product can survive a bad ad campaign. It may not survive bad landed-cost math.

De minimis made many low-value direct imports look simpler than they were. Once duties and processing costs apply, the unit economics of low-ASP products need to be rebuilt from the border inward.

The August 2025 end of de minimis treatment for low-value shipments changed the economics for sellers who depended on small, direct-to-consumer cross-border parcels.

For the low-ASP squeeze, this is not theory. It shows up as a tighter bank balance, a weaker reorder plan, or a month-end margin number nobody can explain. Teams miss it because sales, orders, warehouse movement, and accounting each show only part of the operating record.

Read de minimis is dead as an operating routine. By the end, the low-ASP squeeze should have a calculation, a review owner, a channel check, and a clear rule for what changes when the number moves.

Start with the low-ASP squeeze

A $15 item with $6 supplier cost, $4 freight, $2 duty and brokerage allocation, $2 marketplace fees, and $1 packaging has no room left for ads, returns, or profit.

The point is not to memorize another metric. The point is to expose the specific operating gap behind the low-ASP squeeze before the platform, customer, or bank account exposes it for you. Strong sellers do not wait for quarterly reports to learn which products, channels, or workflows are weakening the business.

Use the low-ASP squeeze as a working lens. It should help you decide whether to reprice, pause a SKU, change a fulfillment path, renegotiate a supplier term, or stop spending on a product that looks successful only because the costs are scattered.

Where the low-ASP squeeze crosses team boundaries

The low-ASP squeeze matters most for sellers operating across more than one channel, more than one fulfillment route, or enough SKUs that manual review has become selective. A single-channel seller can often catch the issue by looking directly at the storefront and bank account. A multichannel seller cannot. The same order can touch Amazon, Shopify, Walmart, eBay, TikTok Shop, a 3PL, a carrier, a return portal, an ad campaign, and an accounting export.

The warning sign is not complexity by itself. Complexity is normal once the business grows. The warning sign is when the team cannot say who owns the low-ASP squeeze and which system proves the answer. When the answer depends on who you ask, the operation is already carrying hidden risk.

Founders should care because the low-ASP squeeze can reduce cash without reducing revenue. Operators should care because it creates recurring exception work. Finance should care because blended reports hide cross-subsidy. Support should care because customers feel the downstream effects as cancellations, late shipments, refund confusion, and inaccurate promises.

The records that make the low-ASP squeeze measurable

Do not start with a dashboard. Start with the raw facts behind landed cost for de Minimis Is Dead: ninety days of orders, SKU-level cost, channel fees, fulfillment cost, return outcomes, ad spend where relevant, and every adjustment that changed the result.

Each row for de Minimis Is Dead should answer five questions: what sold, where it sold, what it really cost, what happened after purchase, and what decision changed because of it. If a field is missing, mark it unknown rather than hiding it inside an average.

Separate channel data before judging the low-ASP squeeze. Amazon fees, Shopify payment costs, Walmart marketplace rules, eBay buyer behavior, TikTok Shop spikes, and wholesale exceptions do not behave the same way. A product can deserve promotion in one channel and deserve a pause in another.

• Order-level sales, refunds, discounts, and shipping revenue.
• SKU-level landed cost, packaging cost, marketplace fee, and payment cost.
• Fulfillment method, warehouse, carrier, promised date, and delivery result.
• Returns, reimbursements, claims, cancellations, and support contacts.
• Manual overrides, spreadsheet edits, direct channel changes, and approval notes.

The calculation that exposes the low-ASP squeeze

Use this as the first-pass calculation for the low-ASP squeeze. It is not perfect accounting, but it is enough to decide whether the issue is worth a deeper audit.

Landed cost = supplier cost + freight + duty + brokerage + insurance + prep + packaging

Run landed cost for de Minimis Is Dead across your top 20 SKUs, then run it again by channel. A product that looks healthy in blended reporting can become a cash drain once marketplace fees, payout timing, return behavior, storage cost, or fraud are separated.

Do not argue about precision on the first pass of the low-ASP squeeze. A rough but complete model beats a precise model that ignores a major cost bucket. The first version should be good enough to sort the catalog into four groups: obviously healthy, probably healthy, questionable, and dangerous.

The most useful de Minimis Is Dead model is reviewed on a cadence. Weekly is right for fast-moving sellers, monthly is acceptable for slower catalogs, and every major fee, supplier, ad, or fulfillment change deserves a fresh run.

Reading landed cost without fooling yourself

A good result is not simply a higher number. A good result is a number the team can explain. If landed cost in de Minimis Is Dead points to a problem but nobody can identify the cause, keep drilling. The cause may be a fee change, mapping error, return pattern, fulfillment mismatch, stale promotion, or channel-specific SKU behavior.

Look for direction before perfection in de Minimis Is Dead. If the result has worsened for three consecutive review cycles, it deserves attention even while the exact dollar amount is being refined. If the result swings by channel, the product is probably being managed too broadly.

Use thresholds. Decide in advance that duty is estimated at order level instead of SKU level triggers review. Thresholds remove politics from the process. The team is no longer debating whether a problem feels urgent; it is following an operating rule.

The traps hiding inside the low-ASP squeeze

The recurring failure modes around the low-ASP squeeze are predictable, but the exact leak depends on this article's operating context. They are not signs that the team is careless. They are signs that the business has outgrown manual stitching between systems.

1. Duty is estimated at order level instead of SKU level.

For the low-ASP squeeze, "Duty is estimated at order level instead of SKU level" is the point where the post stops being analysis and becomes an operating audit. It tells the team which assumption must be proven before anyone changes price, inventory, channel exposure, or policy.

Start with the most recent ten affected orders and rebuild the timeline from order creation to final adjustment. Use landed cost for de Minimis Is Dead as the scorecard. If the team cannot trace the number without opening private spreadsheets, the issue is not a reporting issue. It is a control issue.

2. Brokerage and processing fees are ignored on low-value shipments.

For the low-ASP squeeze, "Brokerage and processing fees are ignored on low-value shipments" is the point where the post stops being analysis and becomes an operating audit. It tells the team which assumption must be proven before anyone changes price, inventory, channel exposure, or policy.

Compare the channel export with the warehouse or finance record and mark the first timestamp where they disagree. Use landed cost for de Minimis Is Dead as the scorecard. If the team cannot trace the number without opening private spreadsheets, the issue is not a reporting issue. It is a control issue.

3. Old retail prices are kept after import economics change.

For the low-ASP squeeze, "Old retail prices are kept after import economics change" is the point where the post stops being analysis and becomes an operating audit. It tells the team which assumption must be proven before anyone changes price, inventory, channel exposure, or policy.

Look for the manual workaround that made the last incident disappear, because that workaround is often the hidden control point. Use landed cost for de Minimis Is Dead as the scorecard. If the team cannot trace the number without opening private spreadsheets, the issue is not a reporting issue. It is a control issue.

4. Sourcing decisions use supplier price instead of landed contribution margin.

For the low-ASP squeeze, "Sourcing decisions use supplier price instead of landed contribution margin" is the point where the post stops being analysis and becomes an operating audit. It tells the team which assumption must be proven before anyone changes price, inventory, channel exposure, or policy.

Separate the SKU, channel, fulfillment route, and owner so the review does not collapse into a blended average. Use landed cost for de Minimis Is Dead as the scorecard. If the team cannot trace the number without opening private spreadsheets, the issue is not a reporting issue. It is a control issue.

Choose the next move from the evidence: the low-ASP squeeze

Once the low-ASP squeeze is visible, avoid vague next steps. Every reviewed SKU, channel, or workflow should land in a decision table: keep, reprice, re-channel, bundle, restrict, renegotiate, automate, or cut.

A decision table keeps the work practical. It stops the low-ASP squeeze from becoming another interesting analysis that does not change operations. The team should know what will be different next week because the issue was found.

• Keep: the economics and operating workload are healthy enough to leave unchanged.
• Reprice: the product works only if price reflects current fees, returns, or fulfillment cost.
• Re-channel: the SKU is viable on one channel but weak on another.
• Bundle: low average order value or shipping economics need a larger basket.
• Restrict: inventory, fulfillment, or policy risk requires channel limits.
• Cut: the product consumes more attention and cash than it returns.

Controls to install after the review: the low-ASP squeeze

The playbook below turns the low-ASP squeeze into repeatable work. Treat it as an operating SOP, not a one-time analysis.

Step 1: Recalculate landed cost for every imported SKU under $25 ASP.

In this finance article, "Recalculate landed cost for every imported SKU under $25 ASP" is the control being installed. Name the owner, the source system, the exact report or event used, and the decision that changes when the answer is known.

The output should be a reusable operating check, not a one-off spreadsheet tab. When "Recalculate landed cost for every imported SKU under $25 ASP" is reviewed by finance, operations, and support, all three teams should reach the same conclusion without reconciling three versions of truth.

Step 2: Confirm HS codes and current rates with a broker.

In this finance article, "Confirm HS codes and current rates with a broker" is the control being installed. Name the owner, the source system, the exact report or event used, and the decision that changes when the answer is known.

The owner should be able to explain which field changed, who approved it, and which downstream promise it affects. When "Confirm HS codes and current rates with a broker" is reviewed by finance, operations, and support, all three teams should reach the same conclusion without reconciling three versions of truth.

Step 3: Raise minimum viable price or bundle low-ASP products.

In this finance article, "Raise minimum viable price or bundle low-ASP products" is the control being installed. Name the owner, the source system, the exact report or event used, and the decision that changes when the answer is known.

The review is complete only when the next order, payout, return, or channel update follows the new rule automatically. When "Raise minimum viable price or bundle low-ASP products" is reviewed by finance, operations, and support, all three teams should reach the same conclusion without reconciling three versions of truth.

Step 4: Shift repeat sellers to bulk import and domestic fulfillment where practical.

In this finance article, "Shift repeat sellers to bulk import and domestic fulfillment where practical" is the control being installed. Name the owner, the source system, the exact report or event used, and the decision that changes when the answer is known.

Keep the scope narrow enough to ship this week, then expand it after the exception count falls. When "Shift repeat sellers to bulk import and domestic fulfillment where practical" is reviewed by finance, operations, and support, all three teams should reach the same conclusion without reconciling three versions of truth.

Step 5: Cut SKUs that cannot support duties, returns, and ads.

In this finance article, "Cut SKUs that cannot support duties, returns, and ads" is the control being installed. Name the owner, the source system, the exact report or event used, and the decision that changes when the answer is known.

The output should be a reusable operating check, not a one-off spreadsheet tab. When "Cut SKUs that cannot support duties, returns, and ads" is reviewed by finance, operations, and support, all three teams should reach the same conclusion without reconciling three versions of truth.

How to operationalize the low-ASP squeeze in 30 days

Days 1-7: build the de Minimis Is Dead baseline. Export the relevant orders, costs, channel fees, fulfillment records, returns, and manual adjustments. Keep a list of every missing field and assumption so the team can see where the operating record is weak.

Days 8-14: run the first landed cost calculation for de Minimis Is Dead and sort the results. Pick the top 20 SKUs or workflows by order volume, margin risk, support tickets, or manual labor. Mark each one as healthy, watch, fix, or stop.

Days 15-21: make controlled changes tied to the low-ASP squeeze. Reprice only the SKUs that need repricing. Adjust channel buffers only where risk is proven. Fix mappings where data is clearly wrong. Move work out of private spreadsheets where it creates recurring disagreement.

Days 22-30: measure the change in the low-ASP squeeze. Compare contribution, cash timing, cancellation rate, return rate, support contacts, manual adjustments, and exception count. If the metric improves but manual workload stays high, the system still needs work.

Channel checks before you trust the number: the low-ASP squeeze

Amazon usually needs the strictest review because fees, storage, reimbursement, Buy Box pressure, returns, and payout timing can all affect the same SKU. Do not let Amazon volume hide weak contribution. A SKU that keeps sales rank healthy but weakens de Minimis Is Dead is still a problem.

Shopify and DTC channels often look cleaner because the seller controls the storefront, but that can create false confidence. Payment cost, free shipping, discounting, support, returns, and warehouse labor still need to be attached to the order before the low-ASP squeeze is trusted.

Walmart, eBay, Etsy, and TikTok Shop each add their own operating quirks. The mistake is to publish the same economics and inventory assumptions everywhere. The right question is whether de Minimis Is Dead still makes sense after that channel's fees, customer behavior, fulfillment expectations, and support workload.

What makes the low-ASP squeeze decay

The first the low-ASP squeeze audit is useful, but the second and third audits are where the value compounds. Fees change, suppliers change, freight changes, return behavior changes, and marketplace rules change. A model that was accurate in January can mislead the team by April.

Decay usually starts with one shortcut: a copied cost, an unreviewed fee, an exception handled in Slack, a manual channel edit, or an old bundle rule. Together they create the gap between de Minimis Is Dead and real operating performance.

Maintenance for the low-ASP squeeze should be boring. Set a recurring review, automate the exports, keep ownership clear, and make exceptions visible. If the process depends on one person remembering to reconcile a spreadsheet, it is not a process yet.

How Nventory makes the low-ASP squeeze auditable

Nventory connects landed cost to SKU, channel, and order data so pricing decisions reflect what the product actually costs after it crosses the border.

Nventory fits at that layer: orders, inventory, catalog data, channel mappings, and fulfillment decisions in one place. When the low-ASP squeeze lives between platforms, one platform cannot fix it alone.

The goal for the low-ASP squeeze is not to make every decision automatic. The goal is to make every decision start from the same operating record. The team can still override a price, hold inventory for a launch, pause a channel, or accept a lower margin for strategic reasons. The difference is that the choice is visible and traceable.

That is the standard for The low-ASP squeeze: fewer hidden assumptions, fewer private spreadsheets, fewer unexplained changes, and fewer arguments about which system is right.

Before this goes live: the low-ASP squeeze

• Replace any category averages with your own last-90-day channel data.
• Confirm all current policy dates inside the relevant seller portal before publication.
• Add screenshots or exported reports that prove landed cost.
• Link this post to the related cash, margin, returns, or multichannel article in the batch.