Kits and combos: why your cost might be lying

The cost of a kit in a marketplace is the sum of the cost of each component that makes it up — period. It seems obvious, but this is exactly where most multichannel sellers lose money without realizing it. Systems that trust a manually entered "kit cost" field are doomed to deliver unreal margins, because that field is almost always zeroed out, outdated, or filled in by guesswork. The result? You think you're profiting from that top-selling combo, but you're actually bleeding margin order by order.

At Jodda, we call this profit intelligence: seeing the real margin of every SKU, including kits, instead of making decisions based on dressed-up data. In this article, we'll break down why the kit cost lies, how to build the correct cost, and what signs indicate your operation is already contaminated.

How the correct cost of a kit is built

A system that does the math right doesn't trust the "kit cost" field. It opens the kit's composition in your ERP, pulls the cost of each component, and sums them up. If the kit is "3 × Product A", the cost is three times the updated cost of Product A — not the value someone typed in once and forgot to update.

This applies to the ERPs most used by sellers in Brazil. In Bling, for example, kits are products of type "kit" with a structure that lists the items that compose it; the correct cost comes from traversing that list. In Tiny, the logic is similar: the kit is a composite product, and the cost is the sum of the costs of the components. In both cases, the calculation is only reliable if the system fetches the updated costs at the time of calculation — and doesn't settle for a static number.

The trap of “was it available at the time?”

There's a technical detail that generates intermittent zero cost and drives any seller crazy. To sum the components, the system needs to query each item in the ERP. If, at that moment, the ERP has exceeded its request limit and a component doesn't respond, a poorly built system simply gives up and falls back to the kit's simple cost — that field we already know is problematic.

The result is the same kit showing different margins at different times: sometimes the cost is correct, sometimes it's underestimated (or zero). The correct behavior, which we adopt at Jodda, is to never record a knowingly wrong cost. If the composition couldn't be assembled, the system should flag the missing data and try again, instead of pretending the simple cost is good enough. Real margin demands data integrity, not shortcuts.

Variations also inherit cost

A sibling case to kits are listing variations. Imagine a t-shirt listing with color and size variations. If one of the variations is actually a kit (t-shirt + freebie), and the system doesn't understand this relationship, the cost of that variation can come out zero or incorrect — even if the rest of the catalog is fine.

This happens because many systems treat each variation as an isolated SKU, without inheriting the composition logic from the "sibling" kit. The fix requires the system to recognize when a variation is a composite product and, in that case, build the cost by summing the components, just as it would with a traditional kit. Without this intelligence, the margin of specific variations is flawed, and the seller makes decisions based on partial data.

How to tell if your cost is lying

Some classic signs of wrong costs in kits and combos:

• Kits with margins that are "too good" compared to the individual products that make them up — if selling the kit seems much more profitable than selling the items separately, be suspicious.
• Combos with negative margins that don't make commercial sense — likely the cost is being summed incorrectly or duplicated.
• The same kit showing different margins on different days — a clear sign of the "ERP didn't respond at the time" problem.
• Variations of the same listing with widely disparate margins for no apparent reason — one of them might be a disguised kit.

When this doubt arises, the first place to investigate is the source of that SKU's cost, not the margin formula. The vast majority of the time, the formula is correct and the cost in the database is wrong. A repasse audit focused on kit costs often reveals distortions that skew the entire P&L.

What to take away from this article

• Kit cost = sum of updated components, never the "kit cost" field.
• Wrong cost in the database contaminates the entire margin — no later calculation can fix it.
• A momentary ERP failure cannot become a permanently recorded "crooked simple cost".
• Variations can inherit cost from a sibling kit — the relationship between SKUs matters.
• Strange margin? Investigate the SKU cost before suspecting the formula.

At Jodda, the cost of kits and combos is built from the real composition in your ERP — summing the updated components, respecting variations, and without guessing a simple cost when data is temporarily missing. You see the true margin of each combo, order by order, and stop finding out at the end of the month that your top seller was actually your top loss-maker.