Geins + Dotdigital
Everything you need to connect Geins and Dotdigital: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- Connect in about 15 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Geins
- Open the Geins Merchant Center
- Create or verify the integration user
- Generate or retrieve the Management API key
- Copy the API username and password
- 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. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
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 Geins (29)
| Setting | What it controls | Key |
|---|---|---|
| Api User Username | Enter the username of your Geins API user. | geins_username |
| Categories map | Match categories in your ERP with categories in Geins yourself. | geins_categories_map |
| Create new products | Decide whether new products should be created in Geins. | geins_create_articles |
| Custom attributes/fields to map from ERP attributes | Fill Geins custom/extra fields with values from attributes in your ERP. | geins_custom_fields_map |
| Default Market Id | Choose the Geins market that products should be attached to. | geins_default_market_id |
| Disable new products in Geins | Decide whether new products should be disabled when they are created in Geins. | geins_disable_new_products |
| Exclude Orders created before this date | Choose a date to leave out older orders. | stdintegration_filter_geins_order_created_date |
| External Webshops/Markets Attribute | If your ERP has several webshops or markets, enter the name of the attribute that tells which Geins markets an article belongs to. | geins_external_webshops_attribute |
Show all 29 settings
| Setting | What it controls | Key |
|---|---|---|
| Field to map categories to Geins | Choose how categories from your ERP are matched to categories in Geins. | geins_category_field_to_map |
| Field to map webshop/markets to Geins | Choose how the webshops/markets from your ERP are matched to Geins markets. | geins_market_field_to_map |
| Fields to update | If products are updated, choose which fields in Geins may be changed. | geins_product_fields_to_update |
| Geins Non Stock type | Choose which stock type a product gets in Geins when the article in your ERP is not a stock item . | geins_virtual_stock_type |
| Geins Status for Dropship orders | Choose the status a dropship order must have in Geins before it is synced to your ERP. | geins_sync_dropship_order_with_status |
| Group multiple SKUs on a single product | Decide whether articles from your ERP that share a ParentSKU should become one product with several items in Geins (for example one product in several sizes). | geins_group_multiple_skus_on_single_product |
| Grouped product item name attribute | Enter the name of the attribute in your ERP that should be used as the product item name in Geins for articles grouped by ParentSKU – for example an attribute holding the size. | geins_grouped_item_name_attribute |
| Grouped product name attribute | Enter the name of the attribute in your ERP that should be used as the product name in Geins for articles grouped by ParentSKU – for example an attribute holding the parent's name. | geins_grouped_product_name_attribute |
| Management Api Key | Enter the API key for the Geins Management API. | geins_api_key |
| Management Api Password | Enter the password for the Geins Management API. | geins_password |
| Map article to multiple markets | Decide whether an article can be attached to several markets in Geins. | geins_multiple_markets |
| Minimum stock to add to Non Stock products | Enter the minimum stock quantity to set in Geins for products that are not stock items in your ERP. | geins_non_stock_articles_minimum_stock |
| Pricelist - Currency Price map | Decide which price from your ERP goes into which price list in Geins. | geins_currency_price_map |
| Send hyphen as item name | Decide whether the product item name should always be sent to Geins as a hyphen ( - ), meaning an empty name. | geins_product_send_hyphen_name |
| Set tracking number (if available) | Decide whether the tracking number should be added to the order in Geins. | geins_order_statuses_set_tracking |
| Sum stock from all Warehouses | If your ERP has several warehouses, decide whether Geins should get the total quantity from all of them. | geins_warehouse_sum_all_stock |
| Update Geins External Order Statuses | Choose which external order status the order gets in Geins, based on the order's status in your ERP. | geins_order_external_statuses_map |
| Update Geins Order Statuses | Choose which order status the order gets in Geins, based on the order's status in your ERP. | geins_order_statuses_map |
| Update prices | Decide whether prices should be updated in Geins. | geins_update_prices |
| Update products | Decide whether products that already exist in Geins should be updated. | geins_update_articles |
| Webshop - Market map | Match the webshops/markets in your ERP with markets in Geins yourself. | geins_webshop_market_map |
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 |
Did this page help you?