HOW-TO · OMNICHANNEL POS

Comment exporter les rapports de vente POS et e-commerce

Retailers rarely struggle because they cannot download a CSV. They struggle because store sales, webshop orders, marketplace orders, returns, payment fees and stock adjustments arrive in different reports with different clocks. This guide shows how to export POS and ecommerce sales reports from one operating model using ChannelDock's order-history exports, POS system and stock event history.

Channel
POS, webshop, marketplace
Location
store, warehouse, pickup point
Audit
order, payment, stock event
Export packageCSV ready
Salesreceipt, order ID, channel, locationdaily
Paymentsmethod, payout batch, fee, VATfinance
StockSKU, quantity, reason code, ownerops
one export brief → clean fields → shared close

Research pattern: Shopify, Square and Lightspeed document report exports, but seller forums show the real pain is matching POS orders, online orders and accounting periods after the export.

POS salesreceipts, staff, till and location
Online orderswebshop, marketplace and BOPIS
Paymentscash, card, payout and refunds
Inventorystock changes behind each sale

Avant d’exporter : définissez le contrat de reporting

A good export starts before anyone clicks Download. Agree which question the report must answer, which systems are allowed to contribute data and which identifiers finance will use to check the result.

Pick the closing period

Use a trading day, payout period or accounting month. Do not mix order-date, fulfillment-date and payout-date logic in the same file unless each timestamp has its own column.

Lock the field list

Include order ID, receipt ID, SKU, quantity, channel, location, payment method, tax amount, return status, stock event and adjustment reason. Missing identifiers are the main reason exports become manual detective work.

Decide the owner

Finance owns payment matching. Operations owns stock movement. Store managers own cash differences. Ecommerce owns marketplace holds and cancelled online orders.

Useful rule: export events, not just totals. A sales total can match while a SKU, pickup location or return status is wrong enough to create tomorrow's oversell.

Étape par étape : exporter les rapports POS et e-commerce

Use this process for daily close, month-end reporting, stock investigations, accountant exports and POS migration checks.

Choisissez d’abord la question métier

Start with a clear question: daily sales by channel, payout reconciliation, VAT evidence, stock movement behind revenue, staff performance, marketplace settlement, or product sell-through. The question determines the fields. A generic “all orders” export usually creates more columns and fewer answers.

Common mistake: exporting every available field, then deleting columns differently every week.

Utilisez une seule taxonomie de canaux

Name channels consistently: POS, Shopify, WooCommerce, bol.com, Amazon, Zalando, Kaufland, B2B portal and manual order. In ChannelDock, connect sales channels through integrations so every order carries the same channel logic when it reaches the export.

Common mistake: treating pickup orders as store sales in one report and webshop sales in another.

Filtrez par date de commande et statut opérationnel

Pull the period you need, then segment paid, fulfilled, returned, cancelled, exchanged, pickup-ready and partially shipped orders. This prevents future-dated edits, late returns or open BOPIS orders from polluting a closed period.

Ajoutez les champs de paiement et de versement

For finance, include payment method, payment provider, payout batch, fee, refund amount, gift card use and tax amount. POS cash and card sales should not be reconciled against marketplace payouts without explicit provider columns.

Ajoutez la preuve des mouvements de stock

Every sale line should be traceable to SKU, warehouse or store location, quantity and stock event. If an online order was fulfilled from a shop, that shop should appear as the fulfillment location rather than being buried in notes.

Exportez les grandes périodes en tâche de fond

Large historical exports should run as background jobs. ChannelDock's order-history exports keep finance pulls away from live dispatch screens, so warehouse users can keep processing orders while the report is prepared.

Enregistrez la recette d’export

Store the field list, filters, date logic and owner in a repeatable export brief. When the accountant asks for the same report next month, the team should not rebuild it from memory.

Le modèle d’export qui évite le chaos des tableurs

The practical difference between a useful omnichannel report and a messy CSV is lineage. Each row needs enough context to explain where the order came from, who touched it, how money moved and which stock promise changed.

If finance cannot trace a sales row back to an order and operations cannot trace it back to a stock event, the export is not complete.

Receipt or order
Channel + location
Payment + tax
Stock event
Clean export = stable IDs + status filters + payment lineage + stock evidence

Pièges fréquents des exports

  • Comparing POS sales totals with ecommerce order exports that use a different date basis.
  • Leaving pickup orders, exchanges or partial refunds out of the filter logic.
  • Using product titles instead of SKU or barcode as the matching key.
  • Exporting cash drawer differences without linking the responsible store or register.
  • Sending a spreadsheet to finance without documenting whether tax is gross, net or split by jurisdiction.

Exports POS manuels vs. ChannelDock Order History Exports

Manual exports can work for one shop. They break when the same SKU sells through the counter, webshop, marketplaces and a B2B portal in the same period.

Routine tableur

  • Separate downloads from POS, webshop, marketplace and payment provider.
  • Manual column cleanup changes from week to week.
  • Returns and stock corrections are checked after totals disagree.
  • Large date ranges slow down the operational dashboard.
  • Finance and operations argue from different source files.

Workflow ChannelDock

  • Orders from POS, marketplaces, webshops and B2B flows share one operational layer.
  • Exports carry channel, location, status, SKU and stock-event context.
  • Background export jobs protect active picking, packing and order screens.
  • Repeated report recipes reduce month-end rework.
  • Teams investigate exceptions through stock reconciliation instead of editing spreadsheets blindly.

Explore order-history exports →

FAQ sur les exports de ventes POS et e-commerce

Define the reporting period, choose a shared channel taxonomy, include order IDs and receipt IDs, add payment and tax fields, then export the matching order and stock-event rows. In ChannelDock, use order-history exports when the period is too large for a live dashboard.

At minimum: order ID, receipt ID, date, channel, location, SKU, quantity, gross sales, discounts, tax, refunds, payment method, payout batch, fulfillment status and stock movement reason.

They often use different clocks and definitions. One report may use order date, another payout date, another fulfillment date. Refunds, exchanges, pickup orders, marketplace holds and gift cards can also sit in separate reporting buckets.

Use totals for quick checks, but close finance on order-level exports with payment and tax fields. Totals do not explain which receipt, return or stock correction created a difference.

Daily for operational close, weekly for category and location review, and monthly for accounting. During promotions, new store openings or POS migrations, export daily until the exception rate is stable.

Guides POS et reporting liés

Exports become easier when POS stock, online orders and reconciliation workflows already share the same identifiers.

POS order reconciliation

Match receipts, online orders and stock movements.

Read guide

POS inventory sync

Connect store and online availability.

Read guide

Stock reconciliation

Investigate differences across channels.

Read guide

ChannelDock POS

Run store sales beside ecommerce orders.

Explore feature

Donnez la même vérité de vente à la finance et aux opérations

Use ChannelDock order-history exports to package POS, ecommerce, marketplace, payment and stock-event data without rebuilding the report by hand every month.