Images are ready for a Salla store when they depict the right product, answer buying questions and work in the actual storefront layouts. High resolution alone does not establish readiness. Before implementation, identify the available assets, usage rights, missing views and the product or variant each file represents.
Separate asset preparation from photography. A Salla store launch and rebuild engagement does not automatically include a photographer, studio or new image production. If files are missing, record who will supply them before estimating product-loading work. Otherwise, implementation can become an indefinite wait for material that was never commissioned.
Give every image a buying question
“Professional product photos” is too vague to review. Ask what the shopper needs to see: scale, colour, included pieces, a connector, a fastening or an important surface detail. Once the question is explicit, selecting and approving the image becomes less subjective.
One family may need a clear main view, a detail view and an included-items image. Another may need a different set. Do not impose the same image count across the catalogue merely to simplify pricing. Several near-identical photographs do not compensate for a missing view of the feature that matters.
| Buying question | Potentially useful asset | Implication to avoid |
|---|---|---|
| What will arrive? | The included pieces together | Decorative props are included |
| How large is it? | Approved dimensions or scale context | Unverified dimensions |
| How do colours differ? | A correct image for each colour | A digital recolour is an exact physical match |
| What do the details look like? | A relevant close-up | Unsupported material or quality claims |
| Which packaging is supplied? | The approved packaging version | Seasonal packaging is always supplied |
Create an asset register, not just an upload folder
For each file, record the product code, variant where relevant, sequence purpose, approval status, source and usage-rights owner. Finding a photograph online or inside a supplier document does not establish permission to republish it. Obtain suitable permission and retain its reference without exposing private licensing documents in the storefront.
Keep originals separate from web derivatives. Use filenames that distinguish variant and purpose instead of ambiguous labels such as “new” or “final.” Where suppliers change packaging, use a version or approval date so an older photograph cannot quietly return to a current product page.
Product catalogue design and Arabic adaptation can help organise shared product and asset relationships. A store and a catalogue may use the same approved source, but each needs an appropriate output. A large print-production file should not automatically become the file used everywhere on the web.
Record exclusions as well. If a styled scene includes optional accessories, the image brief should state how the page will distinguish those props from the purchased contents. The merchant must approve the representation; a designer should not guess which objects belong in the order.
Test cropping in the actual theme
Salla documents adding multiple product images. Crop suitability and legibility still need checking in the selected theme and actual display locations. Salla's product setup guide.
Review category cards, product pages, supported zoom behaviour, related-item cards and narrow screens. A bottle may look complete on the detail page but lose its cap in a thumbnail. Important text may become unreadable when the image shrinks. Do not solve that by putting even more text into the image; essential facts should also appear in readable page content.
A website design scope can define responsive image behaviour, spacing and information order. Check current media requirements in the merchant's actual configuration before preparing final derivatives. An old article's dimensions should not be treated as a permanent rule for every theme and placement.
Worked hypothetical example: two perfume sizes
This is an illustration of asset decisions, not a LAB project claim. A merchant sells 50 ml and 100 ml versions with slightly different packaging. The supplier provides an attractive photograph of the 100 ml bottle beside a gift box. That photograph neither represents both sizes automatically nor establishes that the gift box is included.
The team records three missing decisions: an approved 50 ml image, a view of the actual included items, and the commercial status of the gift box. The merchant approves the 100 ml photograph only for its matching SKU. Both size representations are checked on mobile cards. An employee then selects the smaller size and verifies that the imagery and wording do not imply the larger version.
If the missing image is delayed, the merchant can postpone the product or approve another accurate asset. The implementer should not be asked to generate a realistic-looking image that invents the packaging. Any retouching or generation must preserve product truth rather than masquerade as documentary evidence.
The acceptance record should identify the exact approved file. A verbal “the supplier photo is fine” is difficult to apply when several similar versions exist. Keeping that decision with the SKU also makes later catalogue updates less error-prone.
Balance informative detail with loading behaviour
Test a page containing the complete intended gallery, not an empty product template. Review mobile detail, file weight and gallery interaction. Distinguish “this image is heavy” from “this page is slow”: there may be unrelated causes, and removing useful information without measurement is not a sound acceptance method.
Web Vitals guidance distinguishes lab measurement from actual visit experience. Use the available evidence without promising identical results across devices. Web Vitals reference. The useful deliverable is a documented comparison under known conditions, with buying information preserved.
Asset acceptance checklist
- Every published product has accurate, approved images rather than temporary substitutes.
- Depicted colour, size and contents match the commercial record.
- Important features remain visible in cards and narrow layouts.
- Necessary information is available as text, not only inside a small image.
- Sources, rights and original files are identifiable.
- Products awaiting photography or approval have an owner and publication decision.
Frequently asked questions
Is photography included in store development?
Do not assume it. Separate photography, editing, derivative preparation and uploading in the proposal, with a named supplier for each.
Can one image serve several colours?
Only when its use is clear and not misleading. If it does not depict the selected colour, do not present it as evidence of that colour's appearance.
Is there one image size for every placement?
Do not assume so. Verify current requirements and test cards, product pages and mobile layouts. Technical file acceptance does not guarantee a good crop.
Does compression solve page speed?
It may address part of the problem, but it does not prove that other bottlenecks are resolved. Compare real pages before and after under similar test conditions.
A useful next step
Supply difficult product samples with original images and SKU references. Request an asset-coverage review and a trial crop in the intended theme before preparing the full collection.
Sources
Reviewed 26 October 2026: Salla product images and Web Vitals.
