CONNECTED BUSINESS OPERATIONS
A product catalog with clear variants and public content
Maintain product descriptions, categories and sellable variants together, with controlled publication and reusable catalog selections.
A clear responsibility in your daily work
A product name is not the complete offer. Colleagues also need to know which version is sold, what its unit means and which information customers can see. Tsumira separates that descriptive product record from its concrete variants.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Product catalog
Organise product names, descriptions and categories separately from the variants customers can actually select.
Product variants
Give each sellable option its own SKU, whole-JPY amount, tax class, unit and quantity rules.
Product categories
Give colleagues and website readers a consistent way to understand the product range.
Public product pages
Use reviewed catalog content for product presentation while keeping internal records separate.
Describe the product once
Maintain Japanese and optional English names, summaries, detailed descriptions, features and SEO fields. Assign a category and a stable public slug so the offer has a recognisable identity beyond a spreadsheet row. 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.
- Product content has a dedicated descriptive record.
Make each variant specific
Variants add their own SKU, whole-JPY price, tax class, unit and quantity rules. Option groups describe distinctions such as size or package. Active state and ordering help keep the intended selections understandable. 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.
- Separate product identity from variant-level commercial details.
Publish a considered selection
Use draft, review and published states before the product is supplied to public presentation. Review the selected variants and connected quotation use rather than assuming an internal edit creates a complete online shop. 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.
- Published information is projected for connected public use.
A concrete workflow
Prepare the context
Create a product with a meaningful category, stable slug and customer-facing description in the languages you actually maintain.
Review the decision
Add valid variants with explicit units, prices and quantity conditions; check that options distinguish real offers rather than duplicate labels.
Check the result
Review publication and test a representative public page or quotation selection before directing customers to the catalog.
An illustrative working example
Illustrative working example
A studio offers a printed welcome pack. The product describes its contents and presentation; variants distinguish package sizes with different SKUs and JPY prices. The team checks the public wording and quotation selection together, so a customer can identify the intended pack without the product being mistaken for an automatic checkout workflow.
Questions about this topic
Does the product record hold every price?
Commercial values live on variants, including SKU, whole-JPY price, tax class and quantity conditions. The product record supplies the descriptive identity.
Which content languages are stored?
The current catalog has Japanese and optional English fields. A multilingual company website does not imply arbitrary-language product fields or automatic translation.
Does publication include payment and delivery?
No. Public catalog projection is distinct from checkout, payment processing, warehousing and fulfilment. Assess those workflows separately.
Can product offerings be reused in quotations?
Enabled connected catalogs can provide product selections to the quotation workflow. Test the applicable variant and its commercial rules in that actual selection.
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: Compare the product description before planning a catalog handoff.
Google Drive
Workflow concept: Review the preparation step before using an external source: Create a product with a meaningful category, stable slug and customer-facing description in the languages you actually maintain.
Slack
Workflow concept: Check the actual destination before sharing this result: Add valid variants with explicit units, prices and quantity conditions; check that options distinguish real offers rather than duplicate labels.