WooCommerce order contribution
Sales enters product contribution; missing COGS remains a gap.
WooCommerce
Limited accessCalculate WooCommerce order contribution without Shopify assumptions
The REST API supplies orders, discounts, returns and shipping. COGS may come from metadata only when the store actually exposes it.
The connector has not completed live certification for public self-service.
What changes after connecting
Find missing evidence
Netrivo shows which WooCommerce evidence is missing in the selected period.
Explain a result change
Lineage identifies the source and sync that changed the calculation.
WooCommerce → data → result
- 01
Connection
The HTTPS URL and consumer key/secret are tested server-side.
- 02
Synchronization
Orders and line items are imported with WooCommerce IDs preserved.
- 03
Result
Sales enters product contribution; missing COGS remains a gap.
Data used by Netrivo
We show only fields actually supported by the integration. Not every account has to return every value.
| Data | Impact | Condition |
|---|---|---|
| zamówienia | “zamówienia” data is preserved within the provider contract and contributes to woocommerce order contribution. | Only when returned by the source |
| zwroty | “zwroty” data is preserved within the provider contract and contributes to woocommerce order contribution. | Only when returned by the source |
| rabaty | “rabaty” data is preserved within the provider contract and contributes to woocommerce order contribution. | Only when returned by the source |
| wysyłka | “wysyłka” data is preserved within the provider contract and contributes to woocommerce order contribution. | Only when returned by the source |
What Netrivo can calculate
WooCommerce order contribution
The REST API supplies orders, discounts, returns and shipping. COGS may come from metadata only when the store actually exposes it.
Why this connection is not available yet
The connector has not completed live certification for public self-service.
- 01The integration and required data scope are prepared.
- 02The real-account provider test is not complete yet.
- 03We therefore do not expose a form that cannot be completed.
- 04After a successful test, account verification, initial sync and coverage review will become available.
Connection requirements
- A public HTTPS store URL and read-only REST API keys are required. The URL passes server-side SSRF protection.
- An account with read permission for the provider scope.
- Companion cost sources when a complete result requires data outside this provider.
Limitations
- Public self-service awaits live certification.
- Product cost is not a guaranteed WooCommerce field.
- Plugins may alter metadata and status structures.
Questions before connecting
How do I connect WooCommerce?
A public HTTPS store URL and read-only REST API keys are required. The URL passes server-side SSRF protection.
Does Netrivo import historical data?
Historical range depends on the sync window and orders available through the REST API.
How are connection credentials protected?
Credentials are sent only to the backend and stored encrypted. Tokens and secrets are never placed in the browser, public logs or screenshots.
What should I do when the connection test fails?
Check HTTPS, key permissions and REST endpoint availability without redirection to a private network.
What is currently outside the WooCommerce scope?
Public self-service awaits live certification.
Related sources and analysis
Review available sources
The connector has not completed live certification for public self-service.