Account Management, Minimums, And Integration Fees: The Fixed-Overhead Bucket
Account fees, unmet-minimum charges, and EDI maintenance don't flex with volume. Treat them as fixed overhead, not per-order COGS, or your breakeven math will mislead you.
Quick answer
Account management fees, unmet order minimums, EDI/tech integration maintenance, and portal access charges are fixed overhead — classify them as operating expense (opex), not per-order COGS. Allocating them across units inflates landed cost at low volume and hides the real contribution margin per order.
The fixed-overhead bucket in a 3PL invoice
3PL charges that stay flat regardless of order volume — account fees, unmet minimums, EDI maintenance, portal access — and belong in opex, not per-order COGS.
When you audit a 3PL invoice line by line, most fees split cleanly into variable (pick, pack, postage) or landed cost (inbound receiving, duties). A third bucket resists that split: fees you'd pay even if you shipped zero orders this month. These include monthly account management retainers, order-volume minimums billed when you fall short, EDI or API integration maintenance, WMS portal seats, and change-order fees for SKU setup.
Because they don't scale with units, treating them as COGS distorts gross margin — especially in slow months. The correct treatment is fulfillment overhead inside opex, with a separate line in your P&L so you can see what it costs to keep the warehouse relationship open before a single order ships.
This page is the deep-dive on the fixed-overhead row of your 3PL invoice line-item audit. If you haven't classified every fee on the invoice yet, start with the parent audit framework and come back here when you hit the fees that won't flex.
Why these fees are fixed (and why 3PLs structure them that way)
3PLs carry real fixed costs to serve your account: a dedicated ops contact, EDI mappings maintained against carrier and marketplace schema changes, WMS user provisioning, and reserved rack space. Account fees and minimums are how they recover that overhead regardless of your monthly volume.
That's why the fees don't move when your orders do. A €450/month account fee is €450 whether you shipped 400 orders or 4,000. An unmet minimum of 2,000 orders bills the shortfall at your contracted per-order rate — the 3PL has already staffed for that volume.
The allocation trap
If you divide €450 of account fees across 400 orders, you'll book €1.13/order of 'cost' that doesn't exist at the margin. Ship 100 more orders and that number drops to €0.90 — not because you got more efficient, but because arithmetic. Make a pricing decision on that number and you'll underprice growth.
How to identify fixed-overhead fees on your invoice
Pull three consecutive months of 3PL invoices and sort every line item by whether the amount changed with order volume. Fees that stayed identical month-over-month — or changed only when you renegotiated — are your fixed-overhead candidates.
The usual suspects: 'Account Management Fee', 'Monthly Service Fee', 'EDI Maintenance', 'API Access', 'Portal Licence', 'SKU Setup', 'Minimum Order Shortfall', 'Compliance/Chargeback Admin', and any 'Dedicated CS' retainer. If a line reads like a subscription, it is one.
Typical fixed-overhead fees on a mid-market 3PL invoice (€1M–€15M annual revenue brands)
| Fee type | Typical monthly range (€) | Classification |
|---|---|---|
| Account management / dedicated CS | 250 – 800 | Opex – fulfillment overhead |
| EDI / API integration maintenance | 150 – 600 | Opex – fulfillment overhead |
| WMS portal seats (per user) | 25 – 75 | Opex – fulfillment overhead |
| Order volume minimum shortfall | 0 – 2,000 | Opex – fulfillment overhead |
| SKU setup / change orders | 20 – 50 per SKU | Opex (one-off) or capitalise if major |
| Compliance / chargeback admin | 100 – 400 | Opex – fulfillment overhead |
How to classify and model them correctly
In your P&L, create a 'Fulfillment overhead' line inside opex, directly below COGS. Everything in the fixed-overhead bucket goes there. Your per-order COGS now contains only genuinely variable fees — pick, pack, postage, packaging materials, insurance surcharges — which is what you want for unit economics and contribution margin.
For breakeven and pricing decisions, model fulfillment overhead the same way you model your Shopify subscription or your Klaviyo seat: a fixed cost you need to clear each month, not a per-unit load. Your contribution margin per order stays honest, and you can see how many orders at that margin it takes to cover the overhead.
Where SKU setup fees belong
One-off SKU setup charges for a seasonal apparel drop are opex in the month incurred. If you're onboarding 2,000 SKUs for a new category launch and the setup bill is material (say, €40k+), ask finance whether it should be capitalised against the launch and amortised — standard practice for lumpy launch costs.
Experiment ideas: what to do once you've bucketed them
First, calculate your fulfillment overhead ratio: monthly fixed-overhead fees divided by monthly orders shipped. If that ratio is above €1.50/order, you're either under-utilising the account or paying for a tier of service you've outgrown in the other direction. Both are renegotiation triggers at contract renewal.
Second, pressure-test the minimum. If you've paid shortfall fees in two of the last six months, your contracted minimum is miscalibrated — either negotiate it down, or commit to a volume push (paid acquisition, bundle promotions, a Shopify Markets expansion) that reliably clears it. Keep paying shortfall is the worst option.
Frequently asked questions
Opex. Account fees don't vary with the number of orders you ship, so they fail the basic COGS test (cost incurred to produce/deliver a specific unit). Put them in a 'Fulfillment overhead' line within opex so your per-order COGS and gross margin stay accurate.
Ongoing EDI/API maintenance is opex, period. The initial build-out of a brand-new integration can be capitalised if it meets your capex threshold and has a useful life beyond 12 months, but the monthly maintenance bill is always opex.
No. A minimum-shortfall charge is the opposite of a variable cost — it exists precisely because you didn't ship enough. Book it to fulfillment overhead so it doesn't contaminate your per-order unit economics.
Sum all fixed-overhead fees (account, minimums, EDI, portal, admin) for a trailing 3-month period, then divide by orders shipped in that period. This gives you a diagnostic ratio for renegotiation — not a number to add to per-order COGS.
It's cleaner on the invoice but worse for your economics. You lose visibility into what's genuinely variable, and if your volume grows the 'embedded' overhead inflates your COGS unnecessarily. Ask for an itemised invoice at renewal.
They're fixed in the sense that they don't vary with order volume, but they're one-off rather than recurring. Expense them in the month incurred under fulfillment overhead. For a major launch (hundreds or thousands of SKUs onboarded at once), discuss capitalisation with finance.
For brands shipping 2,000+ orders/month, €0.50–€1.00 per order of fixed overhead is typical. Above €1.50/order usually signals under-utilisation; below €0.30 often means the 3PL is under-serving the account and you'll feel it in error rates.
It's a judgement call. Most finance teams bucket them with fulfillment overhead because they're billed by the 3PL alongside operational fees, not procured independently. The important thing is consistency — pick one treatment and apply it every month.
No — they're structured to stay flat within a tier. What you can negotiate is a lower per-order variable rate once you cross a volume threshold, or waiver of the account fee entirely above a certain monthly spend. Push for the latter at renewal.
Fixed overhead is one of three buckets in the full line-item audit — the other two are genuinely variable fees (per-order COGS) and landed cost (inbound/duties allocated to inventory value). Classifying every line correctly across those three buckets is what makes your contribution-margin and breakeven analysis trustworthy.
See Metricuno on your data
Bring your stack — Google Analytics, Stripe, a CRM, anything — and we'll walk through the metric tree that turns your funnel into one number.