CONNECTED BUSINESS OPERATIONS
Sell the right variant with explicit conditions
Give each sellable option its own SKU, whole-JPY amount, tax class, unit and quantity rules.
The right SKU carries the right conditions
Separate unit, quantity and amount instead of inferring them from the product name.
A clear responsibility in your daily work
A product name alone does not specify what a customer is buying. Size, package and quantity can change the commercial conditions. Tsumira represents those choices as variants, so the offer can point to an identifiable selection instead of relying on a note that colleagues interpret differently.
Identify the sellable option
Use a distinct variant identity and SKU for the option customers can select. Check its active state alongside the descriptive product. A variant name should distinguish the actual package or size, not repeat the same vague title across several choices. Review an example quotation selection with the colleague responsible for pricing. Keep the product's descriptive identity separate from its sellable variants. The product record holds the category, names, descriptions and public presentation; variants carry SKU, whole-JPY price, tax class, unit and quantity rules. This distinction helps colleagues understand which part of an offer they are changing.
- Keep each sellable selection unambiguous.
Set price, tax and quantities together
Variant conditions include the amount in whole Japanese yen, tax class and unit label. Minimum, step and maximum quantity rules describe permitted selections. Review them together: a reasonable unit price does not fix an inappropriate quantity step, and a tax label should match the actual commercial treatment. Draft, review and published states govern the catalog's public content. A website integration uses the module's public projection rather than exposing the complete internal record. Preview the actual public result and check the relevant language before making a commercial announcement or directing customers to a page.
- Check amount, unit and quantity constraints as one decision.
Review permitted quantities
A carton selection uses the stated unit and quantity rules.
Use stock settings within their real scope
A variant can distinguish finite and untracked stock handling. That setting is a catalog condition, not proof of a complete procurement, warehouse or fulfilment system. Before promising availability, agree which operational record your team checks and how changes become visible in the enabled sales workflow. Catalog information can supply enabled connected modules, including quotation selection. That connection does not by itself establish a checkout, warehouse or shipping workflow. Agree who owns price changes and variant availability, then test a representative selection wherever the catalog is used.
- Separate a catalog stock mode from a fulfilment promise.
A concrete workflow
Prepare the context
List the actual options customers order and assign a clear variant identity and SKU to each.
Review the decision
Review whole-JPY price, tax class, active state, unit and allowed quantities with the commercial owner.
Check the result
Select a representative variant where the catalog is used and verify the resulting document conditions before sending an offer.
An illustrative working example
Illustrative working example
A supplier offers one consumable in individual units and cartons. Different SKUs and quantity steps distinguish those offers. Sales selects the carton variant and checks its unit rather than multiplying an individual-unit price by memory. The catalog does not independently promise a delivery date.
Questions about this topic
Can variants have separate SKUs?
Yes. SKU and commercial conditions are variant-level information; the parent product retains the descriptive identity.
Can we constrain quantities?
The schema supports minimum, step and maximum quantity rules. Review their behavior in the actual selection flow.
Does finite stock mean full inventory management?
No. Finite versus untracked is a catalog setting, not a complete warehouse or fulfilment guarantee.
Are prices multicurrency?
Current variant amounts are whole JPY. Do not treat regional website prices for Tsumira itself as product-catalog currency support.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Shopify (OAuth)
Workflow concept: Map SKU, unit and quantity conditions before choosing a sellable option.
Google Drive
Workflow concept: Review the preparation step before using an external source: List the actual options customers order and assign a clear variant identity and SKU to each.
Slack
Workflow concept: Check the actual destination before sharing this result: Review whole-JPY price, tax class, active state, unit and allowed quantities with the commercial owner.