This guide covers how to connect Centra to Junipeer and the configuration details specific to Centra as an e-commerce platform.
Overview
Centra is an e-commerce platform designed for fashion and lifestyle brands. It supports multi-market selling, wholesale (B2B) alongside direct-to-consumer (DTC), and has its own product information management (PIM) built in.
In a Junipeer integration, Centra is typically the source system — orders, customers, and product data originate in Centra and are synced to an ERP system for invoicing, accounting, and fulfillment.
Connecting Centra to Junipeer
To connect Centra to Junipeer, you need an API token from Centra's admin panel.
Generating an API token
Log in to Centra's admin panel
Navigate to System → API Tokens (or the equivalent section in your Centra version)
Create a new API token with the permissions required for your integration. At minimum, the token needs read access to orders, customers, and products.
Copy the token — it will only be displayed once
Entering credentials in Junipeer
During the Get Started onboarding wizard (Step 2 — Connect Systems), enter:
API Token: the token generated above
API URL: your Centra API endpoint (typically
https://yourstore.centra.com/api/or similar)
Junipeer will validate the connection. If it fails, verify that the token has the correct permissions and that the API URL is correct.
Typical flows
For a Centra integration, the most common flows are:
Orders: Centra → ERP (the primary flow — syncs orders as invoices)
Customers: Centra → ERP (syncs customer records)
Products/Articles: direction depends on your setup — Centra's built-in PIM means products often originate in Centra
Stock/Inventory: ERP → Centra (keeps webshop stock levels accurate)
Refunds/Credit notes: Centra → ERP
How invoice creation works
In Centra, orders and shipments are separate concepts. An order represents the customer's intent to purchase; a shipment is the actual fulfillment unit.
Invoice trigger: Junipeer creates the ERP invoice when a delivery (shipment) is initiated in Centra — not when the order is placed. This means the invoice is created at the moment Lena (or your warehouse team) confirms the delivery in Centra, giving you full control over when invoicing happens.
If an order ships in multiple batches, multiple invoices will be created in your ERP — one per shipment. This is correct behavior.
For a full explanation of how Centra's order and shipment model works, see Centra orders and shipments — how fulfillment works.
Centra-specific considerations
Duplicate SKUs across collections
Centra allows the same SKU to exist on multiple products — a common pattern for fashion brands that carry the same item across seasonal collections (e.g., Spring/Summer and Autumn/Winter). This creates a challenge for stock synchronization, since the ERP typically expects unique SKU numbers.
Junipeer handles this by prioritizing products based on their status: Active products take priority over Inactive, which take priority over Cancelled. If you encounter stock sync issues related to duplicate SKUs, verify that the correct product (the currently active one) is being matched.
EU cross-border and OSS
Centra provides an isEU field on the country object, which Junipeer can use to determine whether an order qualifies for EU One Stop Shop (OSS) reporting. For ERP systems that require explicit country-to-tax mapping (such as mapping a country code like FR to a specific tax zone ID), this mapping is configured in Junipeer's settings. See the Bookkeeping guide for details on OSS configuration.
Credit invoices and refunds
Centra refund flows require particular attention to ensure that credit invoices in the ERP include all relevant rows from the original order. Known issues to watch for:
Missing discount rows: if the original order had a discount, the credit invoice must include the discount row as well. Without it, the credited amount will not match the refund amount, causing reconciliation failures.
Return fees as shipping: Centra may categorize return fees in a way that maps to shipping costs on the credit invoice. While the total may be correct, the accounting distribution will be wrong. Check the line item mapping in your flow settings.
See the Payout Reconciliation guide for more on refund payout handling.
OSS on credit notes
If your integration uses OSS sales account mapping (Fortnox-specific), be aware that OSS mappings may not automatically apply to credit notes. This means a credit invoice could end up on a different sales account than the original invoice. If you notice tax discrepancies on refunds for cross-border EU orders, check whether the OSS mapping is applied to both invoices and credit notes in your flow configuration.
For troubleshooting common errors, see the Error Codes reference or your connector pair's troubleshooting section.