The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
E-commerce
A packaged cart prices a single product row, and that row is not always what you sell. The real unit is a bottle size in one store and the trim and colour a buyer picks in another. Price and stock belong to that unit, not to the product above it. When your catalogue does not fit the row, we define the unit first, ahead of any product page. A choice the customer makes then carries forward to checkout instead of being asked for again.
Custom e-commerce development shapes the store around your own catalogue instead of fitting that catalogue into the product model a packaged cart assumes. What you actually sell, and what price and stock hang from, is settled before the catalogue and before the checkout. At Kokudankokuya the unit sold is the volume, while the KGM SsangYong sales channel sells the trim and colour a visitor picks.
The first question in building a store is commercial rather than technical: what exactly are you selling? The answer decides how the catalogue is organised and what price and stock hang from.
At Kokudankokuya the answer was the volume. A scent sits in the catalogue as a single product record while the unit sold is the volume, so price and stock are tracked per volume and adding one never means opening another product. We take that choice apart in modelling product variants. Navigation follows the same thinking: scent family and note open a second route beside the category tree, which lets a customer who knows no brand names start from a character and arrive at a bottle.
The KGM SsangYong sales channel answered differently. What is sold there is not the car model but the trim and colour a visitor chooses, each pairing stored with its own price, its own image and its own sales condition. Change a choice and both the price and the car on screen move with it, and payment opens as the continuation of the configurator. Because the selection stays in the same session, nobody configures the same car twice.
The size of the build follows from that answer too. Kokudankokuya answers search and everyday reads straight from its database, so the catalogue never needed another layer and there is less to update through years of maintenance. The KGM SsangYong sales channel shares its software set with the brand’s corporate site, which keeps both systems inside one body of knowledge.
The areas we scope a store project around, starting from whichever one weighs most in your business:
The shop window, product pages, search and navigation follow how your customers actually look for what you sell. At Kokudankokuya the scent family and its notes open a second route beside the category tree.
When a sale needs choices and prices moving together, payment becomes the last step of that same flow rather than a separate form. On the KGM SsangYong sales channel the price updates on screen as the buyer picks trim and colour.
Price and sales conditions attach to the unit you actually sell, so a customer never rebuilds a configuration at the next step. The KGM SsangYong sales channel stores every trim and colour pairing with its own price and its own image.
Stock and order information is tracked the way your team already works. Kokudankokuya keeps a scent as one product record while each volume is its own sellable unit, so adding one never means opening another product.
We do not assume your traffic and add layers for it, because you are the one who maintains them for years. Kokudankokuya's catalogue never reached a scale that called for a separate search layer.
The payment and shipping providers you already use connect at the same point in the sales flow. You choose who you work with, and the connection is built around that choice.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
Buyers pick a SsangYong model, configure it by trim and color, watch the price form from that choice and pay without leaving the flow. The configurator and the checkout are two steps of one flow.
One scent stays a single product record and each bottle size is a separate sellable unit, priced and stocked on its own, so a new size is not a new product. Fragrance family and notes run alongside the category tree, for shoppers who arrive without a brand name in mind.
Your customer picks up the goods and decides in front of you. In e-commerce that decision rests on a written page, and the order record becomes the proof of what was sold.
You have decided to sell online. Someone still has to say which unit you sell, what the price hangs on, and whose name the payment account is in. Read the whole list by its owners.
Asking the new system to print invoices gets you a PDF template. We cover who ends up retyping invoice numbers, what a work order does when nobody answers, and how to retry without sending twice.
When the person writing the quote is not the person who ran the calculation, the same data is typed twice and two prices appear. We trace a chain where every quote line reads back to its input.
Comparing trims without a consultant, a site survey requested from the website, a reading taken without an appointment. The same test weighs each pre-sale step, and each handover leaves a cost.
One scent ships in several sizes, one car in several trims, every used machine is one of a kind. Four live catalogues answer the same question differently: which record holds price and stock?
Keep the brand gold; the costly part is a colour scattered across screens. How many files open to fix a shade, what does the audit miss, and who writes the disproportionate-burden assessment?
None of them; the store is built on the way your catalogue is actually organised. That way your product does not have to fit the fields a template happens to offer. Kokudankokuya keeps a scent as one product record and sells each volume as its own unit. Describe how your catalogue divides up in the quote form and that is enough to start.
It can, and we size the store from your catalogue and the volume you expect. We quote no figures up front and we do not add a layer nobody has asked for, because you are the one who carries its upkeep. Kokudankokuya's catalogue never grew to a size that needed a separate search or cache layer. Tell us how big your catalogue is today and what you expect in season, and the layer decision follows from that.
We can, and which providers you use is settled with you during planning, so none are named here. What matters for you is that payment continues the sale instead of restarting it: your customer's choices arrive at checkout without being entered again. The KGM SsangYong sales channel opens payment as the next step of the configurator, carrying the trim and colour selection into the same session.
We can, and the heavier half of the work is rebuilding the product model rather than copying the data. What you actually sell gets answered before anything moves, so your current store's problem does not travel into the new one. Kokudankokuya settled on the volume as the unit sold, leaving a scent as one product record with price and stock hanging off each volume. If you run an ageing system that still works, the software consulting page carries our evidence for taking one over.