Does every order automatically create an invoice in Frihet?

That should not be assumed. Each connector’s published scope states what it reads or synchronizes. Review client, amounts, currency, tax fields, and numbering before issuing an invoice.

What Shopify scope is published?

The manifest declares reading orders, products, and customers, plus analytics. It does not extend that contract to automatic fiscal issuance.

What do the Gumroad and Lemon Squeezy connectors do?

Their published contracts synchronize sales as income records. Review those records before using them in later processes.

Can I connect more than one source?

The directory contains several live ecommerce connectors. Evaluate and test each connection separately; do not infer shared fields, behavior, or flow direction.

How do I complete a banking review?

Frihet supports OFX, MT940, CAMT.053, and CSV statement imports. External direct bank connectivity is not active.

Ecommerce ERP: Sales Data and Invoicing Under Control

An ecommerce business produces data at several points: catalog, order, customer, collection, refund, and fiscal document. Bringing that information into an ERP can reduce transcription, but only when the workflow distinguishes what is queried, what is recorded, and what needs a decision before becoming an invoice.

A common mistake is treating “ecommerce integration” as a synonym for complete automatic invoicing. One connector may read orders without issuing documents. Another may synchronize sales as income without deciding tax. The published scope of each integration is the boundary that should guide the process.

Three layers that should remain separate

1. Commercial data

Orders, products, and clients describe what occurred in the sales channel. They are the starting point for reviewing buyer identity, descriptions, quantities, and currency.

2. Income or collection record

An income record can represent a sale in financial management. It does not decide the corresponding invoice or replace verification that payment occurred.

3. Fiscal document

An invoice has numbering, issuer and recipient data, dates, amounts, and tax fields. Issuing it is a separate action from importing an order. Review the fiscal context of the transaction before confirmation.

Separating these layers lets a team automate data transfer without presenting an inference as an accounting decision.

Shopify: published scope

The Shopify integration is live in the Frihet manifest. Its published capabilities include reading orders, products, and customers, plus analytics. That contract can bring store context into the ERP and support an orderly review.

The contract does not say that every order issues an invoice, tax is calculated without verification, or a collection changes state by itself. If you need those steps, inspect the current documentation and design the approval process explicitly.

WooCommerce: availability without inference

WooCommerce is also live and has a connector entry and documentation. Its manifest record does not enumerate detailed capabilities, so it would be unsafe to promise a synchronization interval, a particular webhook, or automatic invoice conversion.

A controlled evaluation connects a limited environment, identifies which resources arrive, and reviews how fields are represented. Only then should the workflow become part of normal operations.

Gumroad and Lemon Squeezy: sales as income

The Gumroad and Lemon Squeezy contracts are more specific: both synchronize sales as income records. That wording keeps commercial import separate from an issued invoice.

When reviewing records, check transaction identifier, date, amount, currency, and possible duplication. If the business needs an additional fiscal document, create it through the relevant invoicing process and validate its fields before issuance.

Payment connectors

The Frihet catalog includes payment connectors with live status. When an entry does not publish detailed capabilities, its presence does not demonstrate automatic reconciliation, fee recording, or universal matching between a payment and an invoice.

Stripe Revenue Sync is a separate function with a concrete contract: it imports Stripe payments as Frihet invoices every six hours. Even in that flow, inspect imported records and their fiscal information before continuing.

Banking: import, not direct connectivity

For banking review, Frihet supports OFX, MT940, CAMT.053, and CSV statements. A person obtains the file, imports it, and checks the movements. External direct bank connectivity is not active, so the end of the cycle must not be described as automatic synchronization.

A verifiable ecommerce workflow

Confirm that the connector is live.
Read its scope and documentation.
Connect one source in a controlled environment.
Import or query a small set of records.
Check client, currency, amounts, and identifiers.
Decide whether each record is an order, income, collection, or invoice.
Prepare the fiscal document when appropriate.
Review tax fields and numbering before issuance.
Import a bank statement when you need to compare movements.
Document errors and how to reverse or correct the flow.

What an ERP contributes

The ERP provides a shared place to review information from different channels and maintain business records. An integration reduces repetition when it transports data under a clear contract. Review protects the point where that data gains accounting consequences.

A strong ecommerce workflow is not one that promises everything happens by itself. It is one that shows where each value came from, how it was transformed, and who confirms the result before an invoice is issued.