Your Catalog Grows by Addition, Your Schedule by Multiplication

A box that will not ship until it fits the pallet

A frozen prepared-foods packer is three months into converting its corrugated box program, and one format is holding up the line. The BBQ box does not fit the pallet. The obvious fix is to shrink it, but you cannot shrink it on paper. The product is a breaded country-fried steak that comes off an auto-bagger, and the bags carry trapped air that settles only after they are boxed and sit. Size the box to the theoretical dimension and the packers cannot get product into it as it comes off the line. So the box has to be sized to the as-packed reality, validated with a physical sample filled with real product, and timed against a run that is not scheduled until June. One box. Weeks of resize, sample, and reschedule before it ships a single case. Meanwhile a neighboring master case cannot change at all, because it has to clear a customer's display case, and another format is the last one in the set still waiting on samples.

None of this is dysfunction. It is competent people handling a catalog one format at a time. That is exactly the problem.

The catalog grows by addition; the schedule grows by multiplication

Every SKU you add looks like one more line on a spreadsheet. On the floor it is not additive. A new format has to be sequenced against every other format it shares a line with, qualified against the pallet, the bagger, and the customer's case, and fit into a run window the rest of the catalog is already competing for. The catalog grew by one. The changeover graph, the set of transitions the schedule has to navigate, grew by its connection to everything already there. Add formats and that graph expands faster than the catalog does. The planning effort tracks the graph, not the count.

You see the same shape in procurement. A specialty Mediterranean food manufacturer runs a 260-plus ingredient book that keeps growing, driven by customer-specific customization that forces unique inputs, some sourced from as far as France. The supply chain manager carries 80 to 130 RFQs a year. Most of that procurement effort lands on the items that move the least volume, because the high-volume staples sit on long contracts and are settled, while the long tail is where every new customization, new spec, and new RFQ shows up. The bottom of the catalog is where the planning hours go.

That is the tax. The long tail of low-volume SKUs consumes planning and changeover effort out of all proportion to the revenue it returns. It does not show up as a line item. It shows up as a box that ties up an engineer for three months, a procurement desk that spends its year on RFQs for ingredients nobody orders twice, a schedule that gets more fragile every time the catalog gets bigger. The structural advantage you think you are building by saying yes to every customer is quietly being spent on the formats that earn the least.

Price the SKU's load before you add it

The fix is not to cut the catalog blindly. It is to make the hidden cost visible before it is committed. Three moves.

Rank twice. Sort your SKUs by volume, then sort the same list by planning and changeover hours. If the bottom quartile by revenue is eating the top quartile of planning and changeover time, you have found your long-tail tax, and you have found it in numbers you can put in front of a customer or a sales team.

Load the cost into the margin. A SKU's true cost includes its changeover minutes and the RFQ and qualification hours it pulls every year. When the BBQ box's three months of resize-and-sample work is priced into the box, the conversation about whether to run it at all gets honest. Most plants never do this, so the tail looks free.

Model the load before you commit. The same operators who will model an entire sausage line to within 2 percent of a full year of actuals before they move one shift of capacity will add a SKU on a hallway yes. One operator built a digital twin of its facility, validated it to 98 percent of a year of real data, and used it to test consolidation from four lines on one shift to two lines on two shifts before spending a dollar. Bring that discipline to the catalog. If you would model a line before you change it, model the changeover graph before you add to it.

What a well-run catalog looks like

Every active SKU carries a loaded cost that names its changeover and planning minutes, and that number is in the margin. The bottom-volume quartile is reviewed on a fixed cycle for sunset or batched into a single scheduled run instead of scattered through the week. No active format needs bespoke pallet, line, or sample handling to ship; the ones that do are either fixed or retired. New SKUs clear a gate that prices their planning load before sales commits them, not after the floor discovers it.

The catalog is not your advantage. The catalog you can actually run without taxing every other format is. Nobody loses structural advantage to a competitor as fast as they spend it on their own long tail.