A product displays a blue image although the customer selected a different lid, while the quantity belongs to another variant. Counting products uploaded to Salla will not reveal this problem. Catalog acceptance should follow what the customer selects through to what staff would actually prepare.
When commissioning catalog preparation, begin with a sample representing options, images and references. It defines content, entry and verification work and distinguishes uploading a file from taking responsibility for correcting the customer-facing result.
Define what you sell before generating combinations
Imagine a fictional home-organizer store with two sizes and two lid types, where one color is unavailable in one size. Do not assume every mathematical combination represents a real product. The catalog owner defines sellable variants and their approved references, images and quantities.
Include an available and unavailable variant, clarifying whether the latter does not exist or exists but is out of stock. Ask how the proposed store represents that distinction. Confusion can expose an unfulfillable choice or hide a product you intend to replenish.
Include an alphanumeric reference and check it against the approved value after preparation. Ask which field identifies that same variant and how it appears in fulfillment materials. A different marketing name should not leave staff guessing which organizer the customer selected.
An acceptance sheet connecting selection and outcome
Use this sheet on one sample product before scaling the work. Add actual references and reviewer names in your working file, retaining the approved data version so results remain interpretable.
| Element | Define in the sample | Acceptance question |
|---|---|---|
| Product and variant | Size, lid, color and approved reference | Do catalog and fulfillment labels mean the same thing? |
| Image and description | Matching image and selection-specific specifications | Does presentation stay correct after changing an option? |
| Quantity and availability | Quantity source and required display boundaries | Are sold-out and unsold combinations distinguished as agreed? |
| Displayed price | Owner-approved value for each case | Can the customer identify the price for their selection? |
This proposed sheet does not promise every representation in every plan or theme. Salla documents text, color, image and default options. Request evidence in your configuration and clarify combination limits before preparing a large file.
Separate file correctness from presentation correctness
Import documentation distinguishes creating products from updating existing ones and describes templates with required structure. Identify the chosen method, product-matching key and effects of resubmission. A second upload should not become an unexplained source of duplicate products or unrelated changes.
Request checks after processing from customer-facing pages and staff-accessible product records, beyond the upload success message. Identify separately prepared images, text and options. One file cannot be assumed to carry every app's data or support all subsequent updates.
Assign specification and image sources
The store owner should approve dimensions, material, units, images and prices or commission that work explicitly. Content writers should not infer capacity from photographs or copy specifications from similar products. Record missing information for completion instead of filling it with plausible guesses.
Salla's product documentation covers names, descriptions, images, SKUs, quantities and channels. Some features have plan or market boundaries, so do not generalize channel availability across countries. An SEO field also establishes neither guaranteed rankings nor owner approval of everything entered.
Expose a known error before accepting the remainder
In a test environment or controlled sample, deliberately swap a variant's image and ask acceptance steps to detect it without publishing misleading customer data. This distinguishes relationship checking from confirming that some image and name exist. Repeat the same case after correction and record its outcome.
Define batch acceptance, exception ownership and retest timing. Review Salla preparation scope and design versus custom applications. Send the sample when requesting Salla implementation with Nextwave so catalog volume and relationships are understood before pricing.
Catalog references
Salla documentation on imports and updates, product options and physical products was opened on 4 November 2026. The original example and sheet involve no file upload or store modification. AI assisted preparation, with information and translation review.
