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" and 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 mobile companion, on iOS or Android, both read from it. Five storefronts converge into one company-wide knowledge graph, and the per-product dossier is one view onto it.

Lemnia reads where the orders, returns and reviews actually live.

• WooCommerce + PrestaShop

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

• Amazon Seller IT

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

• Stripe + PayPal + Satispay

  Payment intents, disputes and 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. The ticket is cited under the dossier that triggered it.

Where multi-channel actually saves time.

• Product · SKU trend

  The life of a SKU across all storefronts: orders, returns, reviews, tickets. The descriptive margin is computed from issued invoices and warehoused cost, and the trend is reconstructed from the data rather than projected blindly.

• Customer 360 summary

  A customer's whole history regardless of the storefront they bought from, gathered from orders, payments, communications and tickets, cited line by line.

• Receivables and cash forecast

  Three payment processors and an aging schedule by band, consolidated, with the projected balance at 30, 60 and 90 days. It stays descriptive, and every line traces to the invoice that generates it.

• Management digest

  Weekly anomalies and a quarterly read for management, with sales by channel and product, receivables and recorded decisions. Exportable as a signed PDF for the Monday meeting.

• GDPR + AI Act compliance

  DPIA state, access log, sub-processor list and the AI Act art. 50 trail in a single BLAKE3-signed PDF for the DPO or the auditor.

Descriptive only, even at scale.

Even at 10,000 orders a month, Lemnia stays a descriptive tool. There is no predictive churn scoring on customers, no automated price adjustment and no rating of customer reliability. The R7 trend reconstructs a curve through invoices already issued, and it is not a forecast that decides who to place 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 under CST.396, is the only path Lemnia provides, and it runs only when the operator triggers it on a single order, in front of the screen.