Orders, returns, reviews in one dossier.

Three storefronts, two marketplaces, one payment processor, no single truth.

A multi-channel e-commerce operation talks to itself in five languages. WooCommerce calls an order "order". PrestaShop calls it "commande". Amazon Seller calls it "orderItemId". Stripe calls it "payment intent". When the customer writes back asking about "my order from last week", the operator has to guess which system holds the truth.

Lemnia T2 sits on a Mac mini or a dedicated NUC on the local network. The desktop client and the iPhone companion both read from it. Five storefronts, one per-product dossier.

Read where the orders, returns and reviews actually live.

• WooCommerce + PrestaShop

  REST API ingestion of orders, returns, refunds, product variants. Reviews and Q&A threaded under the SKU dossier.

• Amazon Seller IT

  MWS / SP-API for orders, settlements, returns. Per-ASIN dossier joins Amazon traffic with the in-house warehouse and ERP.

• Stripe + PayPal + Satispay

  Payment intents, disputes, chargebacks. Lemnia reconciles the payment side to the order side without exposing card data.

• Zendesk + WhatsApp Business

  Customer threads tied to the order ID and the product SKU. Ticket cited under the dossier that triggered it.

Where multi-channel actually saves time.

• R2 — Product recap

  Life of a SKU across all storefronts: orders, returns, reviews, tickets. Descriptive margin computed from issued invoices and warehoused cost.

• R5 — Cash flow

  Three payment processors plus 30-90 day customer aging, consolidated. The receivables panel says exactly where the cash sits today.

• R6 — DSO

  Receivables aging per customer regardless of which storefront they bought from. Reminders cited and tracked.

• R7 — Sales trends

  Revenue by channel, product, period. Year-on-year, month-on-month. Pareto (80/20) customer segmentation. Excel signed for the Monday meeting.

• R11 — Connector health

  When Amazon Seller stops returning orders, you see the gap before the customer sees the broken stock figure.

Descriptive only, even at scale.

Even at 10,000 orders a month, Lemnia stays descriptive. No predictive churn scoring on customers, no automated price adjustments, no rating of customer reliability. The R7 trend is a curve through invoices already issued — it is not a forecast that decides who to dunk into a retention loop.

The 19 active connectors are all read-only at v0.1.5. Write-back via OmniParser (the read-only customer-elected fallback CST.396) is the only path Lemnia provides — and only when the operator triggers it on a single order, in front of the screen.