Use the Replify integration with Salla

Connect your store in Commerce → Salla. Manage product Knowledge in AI → Knowledge → Salla product Knowledge.

Connect and verify

1. Use a merchant account authorized to install the app. Confirm the store, workspace and messaging channel.
2. Open Commerce, choose Salla and complete secure authorization.
3. Use a demo store or safe test order. Check the customer, order reference, status, product/cart context, sender and event time in the correct workspace.
4. Confirm repeated webhook delivery does not duplicate customer actions.

Never paste access tokens into chat or workspace notes.

Keep product Knowledge current

1. Authorize Products read only. A new installation imports the full catalog once after authorization. For an existing installation, request its first import from the Salla product Knowledge panel.
2. Review indexed products/variants, pending or failed updates, and the last full import and product-event times. Refresh status only reloads status.
3. Choose Refresh a product and enter its Salla product ID to repair one item and its variants.
4. Choose Resync full catalog, review the store and scope, and confirm to fetch every product again. Changed descriptions use metered indexing; unchanged embeddings are reused. A queued request is not completed indexing.

The Assistant can inspect sync status, search current products, read product/variant details, and prepare either refresh for your separate approval. Try “Show my Salla catalog status” or “Resync all products in this store.” AI-management permission and an active authorized store are required. Expired/suspended access must be restored before processing.

Subscribed product events update affected items without hourly or daily full scans. Deleted, unpublished or channel-ineligible products are removed from AI search after an event or live verification. Current prices and availability are checked before answering. Products, prices and stock cannot be edited through this integration.

If an event is missed or an edit has no event coverage, discovery may stay stale. A recent event does not prove the whole catalog is current. Request a manual resync after a known delivery gap or stale result; reconnecting alone does not launch one. Interrupted received jobs retry; unresolved failures need review and a product refresh or manual full resync.

Follow order and shipment updates

1. Open Commerce → Operations → Carrier monitor. Each shipment row shows the customer's first name and the linked order's Latest status. The filter and Last change follow that order status. When no order status is available, the row uses shipment information.
2. Click anywhere on the row, or focus it and press Enter or Space, to open one chronological timeline. Order updates use the default dot. Verified shipment webhooks use a pink dot and Carrier Update pill; matching delivery milestones appear once as an order update. Shipment data fetched during an order refresh updates the details without adding another timeline entry or overriding the order status. Shipment status in the details can differ from the order. Creating AWB label means generation is pending, not that an AWB is issued. Selection checkboxes and tracking links keep their own actions. Creation dates stay fixed in Salla's timezone; missing carrier creation times stay unknown.
3. Keep the page open: received order-created/status events update the order and actual linked shipments, and order-status events also update the pipeline deal. The page reloads after processing and when revisited; neither reload imports the whole store. Only shipments appear in Carrier monitor; analytics still use your selected date range.
4. Use Refresh data for the initial operations import or recovery after missed events. Workspace settings permission is required. There is no scheduled six-hour refresh.

Keep shipment.created, shipment.updated and shipment.cancelled enabled in Salla: they cover label, tracking, cancellation and shipment-only changes. Order-status payloads can include shipping/tracking numbers and label fields, but empty values do not confirm an issued AWB. A completed order does not prove delivery. If data stays old, check webhook delivery, authorization and processing failures before a manual refresh. Empty shipment results preserve recorded shipments. Outbound messages still require the configured consent, sender and template checks.

Read inventory prices and discounts

1. Open Commerce → Inventory after connecting your Salla store.
2. Select Refresh data to import current product and variant prices and stock.
3. Each card shows the synced price and currency, variant option labels, its own SKU when provided, the parent SKU, branch and stock quantity. Unlimited stock is labelled Unlimited. When the same variant's regular price exceeds its current price, the card shows the crossed-out regular price, discount percentage and amount saved.
4. Search by the parent SKU to find every variant, including variants with a different or missing SKU. Search also matches option labels. The page URL keeps your search, stock status, category, branch and inactive-product filter after a browser reload or Refresh data.

Products with variants show their individual stock lines. An older parent stock row is excluded from current inventory and forecasts so it cannot create a false stockout or double-count stock; its stored history is retained. Option labels come from the store. If the store has not supplied them, the card shows the variant ID until refreshed.

Missing pricing shows Not provided until a successful refresh or product update supplies it. Cards use the last synced prices; they are not checkout quotes and do not include cart coupons or extra checkout charges. Products, prices and stock remain read only. Existing stock history, demand and reorder guidance stay on the card.

Stock history and the pink reorder threshold use smooth curves. Hover over either chart to see the date, stock, ordered units (not paid sales) and reorder threshold together.

For each date, the threshold is rounded up from its trailing average daily ordered units × (forecast days + safety-stock days). The demand-history setting controls the trailing window, including that date; later orders are never included. Canceled and returned orders are excluded. If less history is retained, the estimate uses the available recorded days and the hover shows Demand days. Dates without usable demand show no threshold. Longer chart ranges group sales into buckets and show the threshold for the last date of each bucket.

The line is recalculated using current monitoring settings and retained order statuses, rather than saved past settings. It can rise or fall with demand, or stay flat when demand is steady. The illustrative example toggle is removed. Existing mock orders also count while present. Ask the Assistant to read a product’s inventory history for a date range; this is read only and does not change stock or reorder settings.

Configure useful workflows

• Select needed events: order confirmation, shipment updates, delivery exceptions, cart recovery or post-delivery follow-up.
• Set customer messaging, templates, quiet hours, consent and escalation rules.
• Use approved WhatsApp templates for proactive messages outside the service window.
• Use automations for known events and AI for approved policies, missing details and summaries. Refunds, account-specific changes and exceptions need human control.

Events missing or interrupted?

Settings → Billing identifies Salla-managed subscriptions and links to Salla for plan changes and renewal. Authorization checks the current Salla subscription; a failed check stays pending for retry. A demo store without a subscription needs an explicit platform-administrator demo grant. Demo access enabled identifies that grant; it creates no paid renewal and keeps normal usage limits and action approvals. Live stores cannot use demo grants. Uninstall and manual suspensions still block demo access.

Uninstalling the Salla app disconnects the store and suspends workspace access. In the administrator's account list, Uninstalled means the subscription is still valid; Inactive means the subscription has expired. Sign-in opens a recovery dialog instead of the workspace. Salla subscribers choose Renew through Salla; if the app was removed, reinstall and authorize it too. Access resumes after the verified renewal and authorization. Uninstalling or reinstalling does not extend a subscription. Direct subscribers see available plans and secure payment options in the recovery dialog; payment must be verified before access resumes. Staff members ask a workspace administrator to renew. A manual administrator suspension still requires administrator help.

Check installation, authorization, store ownership, subscribed events, webhook delivery and workspace mapping. Reconnect through the supported flow.

Accepted events retain a receipt for recovery; duplicates share it. Check the original result before replaying interrupted work. Zid ingestion remains unavailable until provider verification is configured and reviewed.