This guide covers how to connect Norce (formerly Jetshop) to Junipeer and the configuration details specific to Norce as an e-commerce platform.
Overview
Norce (formerly known as Jetshop) is a Nordic e-commerce platform used by mid-sized and enterprise retailers. It offers a headless commerce architecture with strong PIM (Product Information Management) capabilities and multi-market support.
In a Junipeer integration, Norce can act as either a source or destination system depending on the data type. Orders typically flow from Norce to the ERP, while product and customer data may flow in either direction.
Connecting Norce to Junipeer
Norce uses API credentials for authentication.
Obtaining API credentials
Contact your Norce account representative or access the Norce admin panel
Generate API credentials with the required permissions for the data types you need to sync
Note the API endpoint URL for your Norce environment
Entering credentials in Junipeer
During the Get Started onboarding wizard (Step 2 — Connect Systems), enter:
API URL: your Norce API endpoint
API credentials: the authentication details provided by Norce
Junipeer will validate the connection. If it fails, verify the credentials and ensure that API access is enabled for your Norce account.
Typical flows
Norce integrations often have a broader set of flows than other e-commerce platforms, because Norce is frequently used alongside an ERP that acts as the master for products and stock. A typical Norce–Fortnox integration includes:
Orders: Norce → ERP (the primary flow — syncs orders as invoices)
Customers: ERP → Norce (customer records managed in the ERP)
Products/Articles: ERP → Norce (the ERP is often the product master)
Stock/Inventory: ERP → Norce (keeps the webshop stock accurate)
This is a common pattern where the ERP is the "system of record" for products and customers, while Norce handles the storefront and order capture.
Norce-specific considerations
Bidirectional data flow
Unlike e-commerce platforms where nearly all data flows one way (webshop → ERP), Norce integrations frequently have significant data flowing from the ERP to Norce. Products, stock levels, and customer records are often maintained in the ERP and pushed to Norce to keep the storefront up to date.
This means you should pay attention to sync scheduling in both directions. A delay in product or stock sync from the ERP to Norce can cause the webshop to display stale data (out-of-stock items appearing available, or new products not appearing).
Shipment data and logistics
Norce integrations sometimes involve logistics connectors like nShift for shipping data. If your integration includes a shipment sync (for example, sending order data from Norce to nShift via Visma.net), be aware that webhook signals from intermediate systems can be unreliable. See the Visma.net guide for details on webhook fallback strategies.
If you see JSON parsing errors on shipment data syncs, verify that the data format matches what Junipeer expects. Changes to the Norce or logistics provider API can occasionally alter the payload structure.
Migration from Jetshop
If your organization previously used Jetshop and has migrated to Norce, your Junipeer integration may reference legacy Jetshop endpoints or field names. Contact Junipeer support if you encounter issues after a Jetshop-to-Norce migration — the API endpoints and authentication may need to be updated.
For troubleshooting common errors, see the Error Codes reference or your connector pair's troubleshooting section.