A channel product-information sheet should identify one actual product configuration and show where every reusable statement came from. It is a handoff record for a distributor or brand team, not a place to combine all attractive facts from a range of models. Build the sheet after selecting a registered model and before sending copy to a retailer, marketplace or sales partner.
Start with one registered model
Put the AIRITU series, exact model ID and recorded lifecycle at the top of the working sheet. AIRITU identifies R-S001, R-AT001, R-AL001, R-W000, R-W001 and D-D001 as distinct models with different classifications and lifecycle states. A sheet for one model must not silently inherit construction, dimensions or production status from another.
If the team has only selected a series, leave model-specific fields open. Use the product catalog to find the model page, then confirm any needed detail against current model-specific information from AIRITU. A channel sheet assembled by a buyer is not itself an AIRITU-issued specification.
Build a field-by-field source column
For every proposed product line, keep the value, exact source, scope and source revision together. Use only fields confirmed for that model. A statement about the R SERIES level should be marked as series-level; it does not certify fit between a particular device and a particular CORE configuration. If a material grade, pack quantity or accessory relationship is not confirmed for this model and order, leave it as a question.
A simple worksheet can start here:
| Proposed field | Model or configuration scope | Source and version | Current disposition |
|---|---|---|---|
| Exact registered model and lifecycle | One named model | Current model page or specification | Confirm before reuse |
| Construction or dimension | Confirmed model-specific field | Source field and revision | Use only at that scope |
| Pack, aroma or accessory proposal | Selected order configuration | Written project confirmation | Keep open until confirmed |
These are prompts, not completed product facts. The sheet should carry its own revision date and owner so a later reader can tell whether a claim came from a current record or an old draft.
Keep declarations and documents in their own lane
Some public wording is a supplier declaration; it must not be rewritten as a laboratory finding. Documentation is also scoped: a file concerning one formulation, product layer or destination market does not automatically support a different one. Use the B2B document-review guide to check type, version, product/formulation scope and market before citing a file.
Before a channel uses regulatory or market-facing wording, obtain the applicable review. Do not add a certification mark, absolute safety statement or unsupported outcome claim to complete the layout. A blank line is more accurate than an inferred approval.
Treat images and commercial fields as references
A photograph can identify what is visible, but it cannot prove a hidden specification, every available configuration or stock for a new order. Record the product photo used, the model it shows and a factual caption. Keep the image caption separate from the sourced product fields.
Likewise, price, MOQ, packaging and schedule belong to the selected project and quotation. AIRITU provides project-specific pricing, and the final schedule is confirmed in the quotation or order approval. Do not paste another buyer’s terms into a distributor sheet.
Approve the current version before reuse
Have the teams responsible for product details, commercial terms and market-facing claims check the current version. Preserve unanswered fields rather than masking them. When a change arrives, issue a new sheet revision and record which source changed. Use contact AIRITU to request clarification for the exact model and market, not a generic promise that every field can be filled.
The result is a controlled input for a channel discussion. It becomes public-facing copy only after the applicable facts, rights and approvals are confirmed for that use.