CONNECTED BUSINESS OPERATIONS
Organise products with clear, ordered categories
Give colleagues and website readers a consistent way to understand the product range.
Categories organise the range; variants define the sale
Use clear product families and an intentional display order.
A clear responsibility in your daily work
A shared business record serves colleagues preparing an offer and people reading the published explanation. Keep those audiences distinct. Check what information is being changed, where the result appears and who should review it. One representative example is more useful than assuming an internal edit has already produced the intended public or commercial result.
Keep the source information clear
Categories have their own stable key, Japanese name, optional English name and explicit sort order. Choose terms that reflect how customers distinguish the range. A category groups products; it is not the same as a sellable variant and should not be used to hide an unresolved difference in commercial conditions. 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.
- List the main product groups and choose stable category keys with understandable names.
Review the relevant presentation
Renaming a category changes its reader-facing explanation, while ordering determines how groups are presented where the catalog consumes them. Review the full range before adjusting a single label. A new colleague should understand the grouping without knowing the internal team history or interpreting an unexplained abbreviation. 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.
- Assign products, set the intended group order and check Japanese and optional English labels.
Review the category order
A changed group order changes navigation, not individual selling conditions.
Check the actual use
Inspect representative products after a category change and check their enabled public presentation. Do not assume category maintenance automatically creates a new SEO landing page, changes every published URL or implements a hierarchical store taxonomy. Confirm the actual destination and handle changes to customer links deliberately. 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.
- Review several catalog selections and the public destination before treating the new organisation as finished.
A concrete workflow
Prepare the context
List the main product groups and choose stable category keys with understandable names.
Review the decision
Assign products, set the intended group order and check Japanese and optional English labels.
Check the result
Review several catalog selections and the public destination before treating the new organisation as finished.
An illustrative working example
Illustrative working example
A supplier separates starter kits, replacement parts and consumables. Categories describe those product families; sizes remain variants within a product. The owner checks a sample from every category before sharing the revised catalog with sales. This example does not claim a specific company has adopted Tsumira.
Questions about this topic
Are categories the same as variants?
No. Categories group descriptive product records; variants carry the conditions of an actual sellable option.
Does a category create an SEO page automatically?
Do not assume this. The category schema and the enabled website composition must be assessed separately.
Does this publish every edit automatically?
Do not assume so. Review draft, review and published state and inspect the actual enabled website destination.
Can AI changes bypass review?
No. Treat proposed wording or updates as reviewable work and respect the user’s actual editing and publication permissions.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Sheets
Workflow concept: Review category names and order before reorganising the range.
Google Drive
Workflow concept: Review the preparation step before using an external source: List the main product groups and choose stable category keys with understandable names.
Slack
Workflow concept: Check the actual destination before sharing this result: Assign products, set the intended group order and check Japanese and optional English labels.