Integration Card

Search Centra Integration Setup

General

• Type – is set to GRAPHQL as it is the most common API used for integration with Centra from ERP systems.
• Default Market ID– set to main market, mandatory
• Latest Run – last time the integration was run
• Orders Synced at– last time orders were synced to Centra
• No. – the name ofthe integration. Usually set to "PROD / TEST / Development" etc. orif two different integrations are to be run at the same time
• Active – sets whether the integration is activated. If this parameter is not active, nothing happens
• Release Orders Automatically – releases the order after the order has been created

Item

Centra has two internal concepts for handling articles and variants that need to be set up in a certain way, and this means that the articles are displayed in different ways inside Centra Admin and on the web. In order to choose the right one, Centras success manager needs to help and determine how this setting should be made.

1. SKU
2. Id

Item Variant SKU Setup

Defines how the SKU should look when it is sent to Centra. This depends on which variant management is used and is set up together with the success manager from Centra.

Item Variant Id Setup

Defines how the ID should look when it is sent to Centra. This depends on which variantmanagement is used and is set up together with the success manager from Centra. 

Sync Brand Type & Sync Collection Type (extension for Anyware Retail or Pebblestone fashion)

Defines how brand and collection are sent to Centra. For standard BC, choose Core.

SOAP

Defines usersettings and addresses for the SOAP API. These data are provided by Centra andare initiated at the start of the project. Worth noting isthat the Endpoint parameter is dependent on which version of Centra will beused and this is also provided by Centra.
SOAP API is deprecated when integration is converted to Graph QL API.

REST

Defines usersettings and addresses for the SOAP API. These data are provided by Centra andare initiated at the start of the project.

Rest API is deprecated when integration is converted to Graph QL API.

Shipments

Tracking No.Mandatory – if this flag is set, orders without a tracking number will not be imported.

Integration Objects

Integration objects control which messages are to be sent to and from Centra.

Supported objects are

1. Item – itemmessages
2. Sizechart -atorleks bows
3. Warehouse -warehouses
4. Stock – inventorybalances
5. Price – pricelists
6. Orders – incomingorders
7. Order status -order update to Centra
8. Return orderstatus – return order creation/update to Centra
9. Customer -customers
10. Shipment Terms –needed to be able to send customers to Centra
11. Payment Terms -needed to be able to send customers to Centra
12. OrderLock – locksorders for change in Centra
13. EventDone – sendsend status on various Events in centers. Used only in the SOAP API
14. Cancelorder –enable cancellation of orders from BC

The most common messages needed for a functioning integration are 1 – 7 and 13. The others do not need to be switched on. For B2B, 9 – 11 are also used as they are required for customers to be created correctly.

Cross References

In this table, Centra codes for payment methods, shipping methods and order types are referenced and can be mapped to BC Codes.

Markets

Market is a central concept in Centra to link settings and flows to. BC uses this to map settings for how information is to be sent and retrieved from Centra.

    General

• Integration no. – defines towards which integration the market belongs 
• Market Id – the ID in Centra to which the set should be linked 
• Country/Region – used for information about what market is being configured and for understanding 
• Description – used for information about what market is being configured and understanding 
• Active – activates the market for the integration 
• Type – defines whether it is Retail or Wholesale 
• Centra Store – indicates the corresponding store in Centra

    Misc

• Location – specifies which standard warehouse location an order should be placed against 
• Price Calculation Method – specifies the type of price calculation used for Centras price lists 
• Customer Price Group – which customer price group should be used if Price Calculation Method is set to Customer Group 
• Currency Code – specifies which currency code is used for the price list

    Order

• Import order with message status – when the order update comes to BC with every status update in Centra, the status when the order can be updated is set here 
• Is B2C – if this is ticked will come  
• Default Customer to be used if filled. If not, the customers account ID found in Centra is used 
• Forwarding service to be added to the order based on what was added to the order when placing the order in Centra 
• Payment methods are set based on what was entered on the order when placing the order in Centra 
• Default Customer – see Is B2C 
• Use Center Customer No. - when entering the order, Centras customer number will be used to try to map the customer to be added to the order 
• Customer Temp. – about Customer Templ. is completed, a customer will be created in BCs customer register using the template specified here 
• Salesperson Code – indicates which salesperson the order is linked to 
• Shipping Type – defines which shipping partner is used. In the standard integration, this value is set to none, but if another party is used, this can be switched on here 
• Prices Incl. VAT – Set at order level if the prices include VAT which has been sent to Centra 
• Capture on Order Confirmation – sends capture flag to Centra in the Order Update message, to activate e.g. Klarna 
• Release Order Automatically – specifies whether orders coming in from Centra should be released automatically 
• Ordertypes to Release – specifies which order types are to be released automatically 
• Archive order automatically – the function automatically archives orders as soon as they are read from Centra

Foreign VAT - added & deducted tax

If Centra is set up to handle extra VAT, this is entered on a separate line against the set up accounting account. An account is set up on the respective market card. The account used is the same account set up in the VAT accounting settings in BC. These settings usually apply to markets outside of EU.

Discounts & Vouchers

On the market card, there is a setting against which accounting account different types of discounts should be posted. This results in a queue of orders coming in if there is a discount in Centra.

AR (extension for Anyware Retail)

• Season Code – season code on incoming orders 
• Order Type – order type of incoming order (B2C)

Marketplaces

It is possible to connect to marketplaces from where Centra receives an order that is sent to BC. This is set up via the market list:

From the Market places list, you connect the standard customer, storage location, payment and shipping method:

Important to note: Source must match the value coming from Centra.

Size Charts

BC detects the type of variant management used in the system. The different variants supported are 

• BC Standard, item variant 
• Pebblestone, item variants with size and color 
• Anyware Retail, item variants with size and color 

Queuing up size charts should preferably be done together with Centra because this is an important basis for how Centra works with variants.

Locations

In BC, locations are configured by adding all available warehouses under CentraIntegration Setup à Locations.

Each locationthat is listed will be used in the messages that send inventory balances forproducts to Centra.

Parameters

Safety Stock – if this field is set, the stock balance will be calculated by the value entered in the field to reduce the risk of overselling.

Items

On the item card in BC there are a number of fields for exists to set metadata that will be send to Centra. 

Countries

The integration with Centra needs to have a configuration for all the country codes that exists on orders that are imported. This is found under Centra Integration Setup -> Countries or Centra log list -> Related -> Setup -> Countries.

Within the EU there is a directive for how VAT should be handled - OSS(https://ec.europa.eu/taxation_customs/business/vat/oss_en). To manage this, it is possible to configure a VAT accounting template and business accounting template for each country code. This means that it is possible to configure all orders placed against a certain country are posted in a custom way. This means that statistics for each country can be produced for reporting tothe Swedish Tax Agency.

Dimensions can be setup by using the action Reports->Dimension.

Products

Updating products is done by

1. A full sync is rigged through the Centra Log List->Actions->Outbound->Enqueue Items function
2. Item Card->Related->Centra->Communication->Send Item
3. Centra Log -> Actions -> Centra Data -> Enqueue Item Data
4. A record change on the item on the below fields

• Item number
• Description 
• Tariff code 
• Country of origin 
• Base unit 
• Centra status

Stock Balance

Stock balances are sent with both the product message and the stock balance message. The inventory balance is sent for all locations, see the chapter for Locations. The balance calculation formula is: quantity in stock minus safety stock, minus quantity on order, minus quantity on outgoing transfer order.

Prices

Prices are sent as a separate message and are sent every time a price list is changed or if a sync is activated via Centra Log List -> Actions -> Outbound->Enqueue Item Price. 

There are two different levels at which prizes are sent

1. Product level – used if no variants exist for items 
2. Color level – used if the item has variants

Price Lists

All prices are triggered by the fact that a price list is published for Centra. Settings for the price list are found under Centra Log List or under Centra Integration Setup.