First establish whether there are no orders in Salla, or whether orders exist but are missing from analytics. The second situation is a measurement problem. If there really are no orders, investigate traffic fit, the offer and the ability to complete a purchase. Give any confirmed checkout-blocking defect immediate priority. Visit counts alone cannot prove that the theme is wrong or that a bigger discount is needed.
This guide is for an existing store receiving traffic, not for launching a new one. The intended output is a documented problem list with an owner, a proposed action and a way to verify each fix.
1. Agree on the numbers before explaining them
Select a clear period and record the source of each number. Do not divide orders from one reporting window by ad clicks from another and label the result your store conversion rate.
Start with a small evidence sheet containing:
- Visits, using the definition in the chosen report.
- Created orders and their statuses, separating tests and cancellations from the outcomes you intend to evaluate.
- Sales, including what the figure includes or excludes: shipping, discounts and refunds, for example.
- Main landing pages, traffic sources, devices and promoted products.
- Dates of important changes: new campaigns, prices, stock shortages, theme changes or installed apps.
Salla provides performance, sales, visits and abandoned-cart reporting. Start with what is available in your account, and verify plan and permission requirements rather than assuming every report is universally available. Salla’s dashboard and reporting guide.
If an advertising platform reports more purchases than the store records, examine conversion definitions, time windows, attribution and duplicate events. The goal is to explain differences, not force every screen to show an identical total.
2. Test measurement without casually changing the live store
Plan an authorized test of a specific journey: open a product, choose an available variant, add it to the cart and begin checkout. Complete a test order only after the owner agrees on the method, any costs and the cancellation or refund procedure. Not every check requires a real financial transaction; choose an approach that fits the store’s setup.
Compare the visible journey with the order record and the events collected by analytics. Record the expected event, observed result, device and time. Check whether reloading a confirmation page causes a purchase to be counted again.
For GA4, DebugView can show events during a test after debug mode is enabled. Privacy controls or lack of analytics consent may affect event visibility, so a missing event alone does not prove that checkout is broken. Google’s DebugView documentation.
When measurement is the problem, request a bounded audit and repair within marketing automation and lifecycle journeys. A tracking defect does not automatically justify a new storefront or a full campaign-management engagement.
3. Does the visitor want what the destination offers?
Once measurement is understood, compare the ad and its destination side by side:
- Is the advertised product available in the displayed size or color?
- Does the page substantiate promises about delivery, packaging or price?
- Can you serve the locations receiving the campaign?
- Is the visitor looking to buy, looking for information, or expecting a different product?
- Does a product-specific ad lead to a generic homepage and require the visitor to find the item again?
Total traffic can increase because a low-intent source has grown while other sources remain unchanged. Review segments rather than relying on the overall average. Do not condemn a whole channel from one campaign; the mismatch may be the creative, offer, product or destination.
Paid campaign strategy and management should connect the quality of the visit to its eventual outcome, not optimize a business report around the cheapest click.
4. Locate the stage that needs investigation
Salla’s conversion report covers the purchase journey and order sources. Its documentation also states that the campaign-performance table shows only campaigns that generated at least one order. A missing campaign in that table does not prove it received no traffic. Salla’s conversion-rate reporting guide.
Use the funnel to choose where to look. A drop-off identifies a stage, not necessarily its cause.
| Where the journey stops | Hypotheses to investigate | Evidence to collect |
|---|---|---|
| Before the relevant product | Wrong destination or confusing navigation | Reproduce the journey from the ad |
| On the product page | Missing information, unsuitable offer or unavailable variant | Inspect buyer questions, imagery and stock |
| Between cart and checkout | Unclear cost or conditions | Compare information available before and after the cart |
| During checkout | Address, delivery, payment or interface issue | Exact reproduction steps, message and device |
| After order creation | Unresolved order state or missing analytics | Reconcile order, payment and measurement records |
Do not infer “the price is too high” from weak add-to-cart activity alone. A visitor may not understand the size, package contents or arrival estimate. Test clarity before reducing price.
Worked example: an abaya store with visits and no orders
This is a hypothetical teaching scenario, not a LAB client case or measured result. Assume a store promotes a specific abaya and its order records show no orders in the period being reviewed.
The investigation starts with observations, not a new theme purchase:
| Assumed observation | Classification | Verifiable next step |
|---|---|---|
| The ad shows a color unavailable on the product page | Offer mismatch | Promote an available product or correct the destination |
| The size selector uses labels without measurements | Content ambiguity | Add approved garment measurements and measuring guidance |
| Delivery cost becomes clear late | Information gap | Explain how customers can determine cost earlier |
| An app overlay covers the checkout control on one device | Journey defect | Approve the change, correct the interference and retest |
The blocking defect comes first, followed by the product mismatch and information improvements. Changing prices, the theme and advertising simultaneously would make later interpretation much harder.
For the covered button, acceptance means completing the affected journey on the relevant devices. For the size guide, displaying the guide is only implementation acceptance. Whether it improves customer decisions needs subsequent behavioral evidence and review of customer questions.
This distinction prevents a common reporting error: describing a completed design task as a demonstrated sales improvement.
Use Salla’s existing capabilities before adding tools
Review the product, delivery, payment, content and reporting options already available to the store. Ask platform support about a reproducible issue with steps and evidence rather than a general statement that “the store does not sell.” An incorrect setting or product record may be the whole problem.
Before paying for an app, document:
- The specific problem existing tools cannot address.
- The intended change to the shopping experience.
- Required permissions, data access and recurring costs.
- How the team will test it and roll it back if it conflicts with the theme.
Do not manufacture urgency, stock shortages or shopper counts to compensate for weak trust. Cart reminders are also not a substitute for fixing the reason a cart was abandoned. Review the available messaging tools, their terms and communication permissions before enabling a flow.
Keep app installation ownership clear. A tool that nobody can configure, monitor or remove creates another operational risk even if its feature list looks useful.
Choose the right scope: audit, optimization or implementation
- You need a documented diagnosis: Start with a UX/UI audit of product, cart and checkout journeys. Request evidence and priorities, not aesthetic preferences presented as conversion findings.
- You have usable measurement and testable hypotheses: Consider conversion rate optimization. Match the experiment to the available data and do not call a brief increase a conclusive win.
- The diagnosed issue requires configuration, restructuring or implementation: Scope Salla store launch and rebuild around the specific catalogue, theme, testing and handover changes required. An existing store does not always need a complete rebuild.
The action list you should leave with
For each issue, record the page, reproduction steps, device, evidence, likely impact, owner, proposed change and acceptance test. Distinguish three labels clearly:
- Confirmed defect: The problem can be reproduced.
- Improvement hypothesis: A plausible explanation still needs testing.
- Unknown: The evidence is unavailable or insufficient.
After implementation, retest the affected journey and its dependencies. Then compare outcomes under understood conditions, recording changes in stock, campaigns and seasonality. A before-and-after comparison alone does not establish causation.
Frequently asked questions
Should I stop advertising immediately if there are no sales?
If a confirmed failure prevents purchases, reduce or pause paid traffic to the affected journey until it is fixed. Without such a failure, review measurement, fit and spending limits before making a blanket decision.
What is a good conversion rate for a Salla store?
There is no single threshold that diagnoses every store. Category, price, source mix, stock and visit definitions affect comparison. Begin with a trustworthy baseline and like-for-like segments.
Will a new theme fix low sales?
Only if it addresses a diagnosed issue without creating another. A theme cannot automatically fix unsuitable traffic, unavailable products or missing product information.
Should I offer a discount or free shipping first?
Understand the objection and the impact on margin and operations before changing the offer. Clear delivery information may answer the question without a discount. A promotion cannot fix a broken checkout button.
Your next step
Prepare the store URL, the period being investigated, available reports without personal customer data, and a list of recent changes. Ask LAB for a focused diagnosis separating measurement, traffic, offer and purchase-journey issues, followed by a repair list with verification criteria. The right answer may be a small correction rather than a new store.
Sources
- Salla: Dashboard and reporting guide.
- Salla: Conversion-rate reports.
- Google Analytics: Monitor events in DebugView.
Reviewed October 26, 2026. Platform interfaces and feature availability can change; confirm the applicable settings in your account before implementation.
