Norce + Dotdigital
Everything you need to connect Norce and Dotdigital: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 15 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Norce
- Open the Norce API account setup
- Create or select the integration client
- Copy the Client ID and Client Secret
- Confirm the correct environment URL
- Paste the credentials into Junipeer
- about 5 minutes
Prepare Dotdigital
- Open API users in Dotdigital
- Create a new API user
- Leave the generated username unchanged
- Set the password and enable the user
- Save and copy the credentials
- Paste the credentials into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. How the data flows
What Junipeer can move between the two systems. The arrow shows which way the data goes.
- Customers
3. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Norce (35)
| Setting | What it controls | Key |
|---|---|---|
| Capture Klarna payment when delivery note is created | Decide whether the customer's Klarna payment is captured (charged) automatically when the order is delivered. | norce_capture_klarna_payment_on_delivery |
| Client ID | Enter the OAuth Client ID that lets Junipeer connect to Norce. | norce_client_id |
| Client Secret | Enter the OAuth Client Secret that lets Junipeer connect to Norce. | norce_client_secret |
| Create Company in Norce | Decide whether new companies should be created in Norce. | norce_create_company |
| Create Customer in Norce | Decide whether new customers should be created in Norce. | norce_create_customer |
| Create Products in Norce [Import products] | Decide whether new products should be created in Norce. | norce_create_products |
| Create product variants in Norce | Decide whether products with variants are created in Norce as one product with variants (a variant cluster) or as simple products. | norce_create_product_variants |
| Default Account ID | Enter the ID of a system account in Norce. | norce_account_id |
Show all 35 settings
| Setting | What it controls | Key |
|---|---|---|
| Default Category [Import Products] | Choose the Norce category to use for articles whose category is not mapped . | norce_default_category |
| Default Culture [Import Products] | Choose the default culture in Norce. | norce_default_culture |
| Default Manufacturer [Import Products] | Choose the Norce manufacturer to use for an article when no manufacturer is set on it, or the manufacturer is empty. | norce_default_manufacturer |
| Default Norce warehouse [Import Stock] | Choose the Norce warehouse to use for stock from warehouses that are not mapped . | norce_default_warehouse |
| Default application ID | Enter your default Norce application ID. | norce_application_id |
| Default status [Import Products] | Choose the default status that articles get in Norce when products are sent to Norce. | norce_default_status |
| Does the price list ID in the other system match the Norce price list code? | Use this if the price list IDs in the other system are the same as the price list codes in Norce. | norce_use_external_pricelist_id |
| Exclude Orders created before this date | Orders created before the date you choose here are not synced. | stdintegration_filter_norce_order_created_date |
| Map Attributes for Product [Import Products] | Connect product attributes in the other system with attributes in Norce, so the values are copied to Norce when products are sent. | norce_map_product_attributes |
| Map Locations (Warehouses) | Connect the warehouses in the other system with the warehouses (locations) in Norce, so stock is updated in the right place. | norce_map_warehouses |
| Map Pricelists | Connect the price lists in the other system with the price lists in Norce, so prices end up in the right Norce price list. | norce_map_pricelists |
| Map Pricelists for NORCE import | Connect a currency with a Norce price list, so prices sent together with products are saved in the right price list. | norce_map_pricelists_by_currency |
| Map customer to Norce application, by country | Choose which Norce application a customer is connected to, based on the customer's country . | norce_map_applications |
| Multiple warehouses on Norce? [Import Stock] | Tell Junipeer whether you have more than one warehouse in Norce. | norce_multiple_warehouses |
| NORCE company code | Choose which value is used as the company code in Norce. | norce_company_code_field |
| NORCE customer code | Choose which value is used as the customer code in Norce. | norce_customer_code_field |
| Norce Checkout Bearer Token | Enter the token Junipeer uses to connect to Norce Checkout, for example to capture or refund Klarna payments. | norce_checkout_bearer_token |
| Norce Client name | Enter your Norce client name. | norce_clientname |
| Norce Company Fields to update | Choose which company fields are updated in Norce. | norce_update_company_fields |
| Norce Customer Fields to update | Choose which customer fields are updated in Norce. | norce_update_customer_fields |
| Norce Region | Enter your Norce region. | norce_region |
| Product fields to be updated [Import Products] | Choose which product fields are updated in Norce when the product already exists there. | norce_product_fields_to_update |
| Select Scope | Choose which Norce environment Junipeer connects to. | norce_scope_production |
| Update Company in Norce | Decide whether existing companies in Norce should be updated. | norce_update_company |
| Update Customer in Norce | Decide whether existing customers in Norce should be updated. | norce_update_customer |
| Update Price active status | Decide whether prices in Norce should also be activated or disabled when prices are synced, based on the price's status in the other system. | norce_update_price_active_status |
| Update Products in Norce [Import Products] | Decide whether existing products in Norce should be updated. | norce_update_products |
Settings for Dotdigital (13)
| Setting | What it controls | Key |
|---|---|---|
| Consent Attribute Fallback | Choose what happens when the customer attribute doesn't contain consent information . | dotdigital_consent_from_attribute_fallback |
| Consent Attribute Field | Enter the name of the customer attribute that holds the consent text. | dotdigital_consent_from_attribute_field |
| Consent Text | Enter the consent text that is attached to a contact when it is created or updated in Dotdigital. | dotdigital_consent_text |
| Consent URL | Enter the web address (URL) where the customer gave their consent. | dotdigital_consent_url |
| Consent from Customer Attribute | Read the consent text from a customer attribute instead of using the fixed Consent Text . | dotdigital_consent_from_attribute_enabled |
| Contact Identifier | Choose how contacts are identified in Dotdigital. | dotdigital_contact_identifier |
| Default Contact List | Choose a Dotdigital list that contacts are added to by default. | dotdigital_default_list |
| List Attribute Fallback | Choose what happens when the customer attribute doesn't contain a list ID . | dotdigital_list_from_attribute_fallback |
Show all 13 settings
| Setting | What it controls | Key |
|---|---|---|
| List Attribute Field | Enter the name of the customer attribute that holds the Dotdigital list ID(s). | dotdigital_list_from_attribute_field |
| List from Customer Attribute | Read Dotdigital list IDs from a customer attribute , instead of (or in addition to) the list settings. | dotdigital_list_from_attribute_enabled |
| Map Country to Contact List | Add contacts to a specific Dotdigital list based on their billing country . | dotdigital_list_by_country |
| Map Customer Attributes to Data Fields (Store) | Write customer attributes to Dotdigital data fields when contacts are saved. | dotdigital_map_attributes_store |
| Map Customer Fields to Data Fields (Store) | Choose which customer fields are written to Dotdigital data fields when contacts are saved. | dotdigital_map_data_fields_store |
4. Troubleshooting
Choose what you see. Each case shows the cause and the solution.
MediumFor error codes and patterns specific to Norce integrations, see the Error Codes
For error codes and patterns specific to Norce integrations, see the Error Codes guide. Common Norce-related issues include:
Refer to the platform setup guide for resolution steps.
5. More guides
Did this page help you?
