An online store’s price tag is not a function of how many pages it has. It hangs on something much narrower: the unit a price is written to in your catalogue, and how much that unit has to hold. Before any of that there is a cruder question, whether a sale can close on your screen at all, and catalogue or ecommerce website settles it; this page starts where that one finishes. The situations that move the figure appear below in the order you usually meet them: the unit the price hangs on, the edge of a package, the work that starts past that edge, and the layer nobody builds. A line-item list would tell you none of it.
Which unit carries the price
Start at the KGM SsangYong Online Store, where one record holds more than a product row can. Every pairing of trim and colour there holds a price, a picture and conditions of sale that belong to that pairing alone, so a single model occupies the database as a grid rather than a line. Set a plain product row beside it, a name, a price, a count in stock, and the gap in work becomes visible: filling a grid and keeping it true is a different job from typing a figure into a field. Where you draw the unit in the first place belongs to modelling product variants; this page uses only the consequence, that the cost follows whatever the unit has to carry.
The KGM SsangYong Online Store composes its figure rather than storing one, and composing costs more to build. Nothing sits there waiting to be read before a buyer chooses; the price comes into being as that buyer assembles the car, out of the configuration they put together. A figure written against a row in advance needs only to be fetched and shown. So when a price exists is the other thing the record decides, after the unit itself.
When a ready-made package fits your catalogue
Where a product record already holds your breakdown, the cost question has an address and it is not ours; it belongs to that package’s own pricing page. So if your catalogue fits a ready-made package, buy the package.
Run the test on a real product: take whatever you sell with the deepest breakdown and try entering it into the package’s product record. Can each combination take a figure, a picture and terms that are only its own? Then the package holds your catalogue and there is nothing bespoke to pay for. Does it all flatten into a single line? Then you are past the edge, and the question changes.
The recommendation to buy the package comes with no conditions attached, and it sits in the middle of the page on purpose. Why the edge falls where it does was worked out in catalogue or ecommerce website, and that argument is not rebuilt here. What this page owes you is the other side of that edge.
What widens the cost when a package will not hold it
The KGM SsangYong Online Store landed past the edge. Off-the-shelf cart software there kept the whole trim and colour split inside one catalogue row, and the breakdown had nowhere to go; the sales channel was written for the catalogue instead. Bespoke work followed from the depth of that catalogue’s own breakdown. Past that edge the figure grows for reasons that sit in the data: the volume of information a record must keep, and a price that gets composed instead of stored. Neither is a screen decision, and trimming design does not bring either down.
Leave the breakdown unwritten and every supplier prices the catalogue it assumes you have; a supplier assuming plain rows prices a shop that is not yours. That is why quotes against one brief drift apart, which why software quotes differ takes gap by gap. That gap is one you can close from your side: the Project description box in our form is where the record behind your deepest product belongs, and it comes before anyone asks about budget.
The layer you never build keeps the cost down
The cheapest layer is the one that never gets built, and the saving is not a screen or a feature but a maintenance line that never opens. A part that was never built cannot fail and never asks to be updated, which is why the absence keeps paying back long after the first invoice. Bespoke, in other words, does not have to mean large: Kokudankokuya’s catalogue asked for neither a search layer nor a cache layer, and the store therefore stands on few parts, with little surface for a maintenance round to cross.
Setup cost and the years after launch are hard to separate, because every layer built is a layer maintained; who maintains software after launch takes that question on its own. KGM SsangYong’s sales channel sits on the same software set as that brand’s corporate site, so whoever keeps one of them standing is at home in the other. A channel on a set your team already knows does not send you looking for a new skill after launch.
One column of the table is where the cost stays small, the other is where it grows, and on every row your catalogue sits in one of them. Mark which, then carry those marks into our form: the Project description box comes under Your project, and the Budget range field opens only after it. How a store gets built on top of these decisions is set out on the e-commerce page, and the quote form is where your catalogue gets written down.