Microsoft Dynamics 365 Business Central LightspeedPos Integration

Process

Stock is synced from Business Central to LightspeedPos. For this we use the last modified date on the stock. This flow only updates products in the LightspeedPos. If a product does not exists it throws a warning where it mentions that the article does not exist.

Please be aware that an actual stock mutation is needed to trigger the flow. So a sales order, purchase order is needed. A correction does not create a trigger for this.

Settings

We support different types of stock calculations by default we send the available stock - sales reservations. You can adjust this if needed.

You can also set the value towards target system if you want to have the stock managed or not. In this way we overwrite the default.

Process

The customer flow is different then the customers that are created via an order. For this the actual trigger is the creation or update of a customer that triggers this flow. We always check first if the customer exists before creating or updating the customer. Addresses are checked and updated if needed.

We differentiate in creating the customer based upon the source data we receive. if we receive from the source a company name we will create a company debtor with the underlying contact. If we receive no company name we will receive a person debtor.

We check if the customer exists per default by email address.

Settings

You can set the mandatory fields for Business Central in settings tab, for example the business posting group.

Data mapping

Per default the flow is mapped so it can work. if you want to make adjustments or additional fields you can do this in the datamapper.

• Customer Name
• Billing address
• street
• Number
• Postalcode
• City
• Country
• Shipping address
• street
• Number
• Postalcode
• City
• Country

Orders can be synced from Microsoft Dynamics 365 Business Central to LightspeedPos or from LightspeedPos to Microsoft Dynamics 365 Business Central.

Process

We retrieve the order based upon last modified date. You can determine in APIcenter if you want to have additional filtering on this. For example if you only want to retrieve orders with the status processing.

Once we retrieved the order data we process it through APIcenter, add missing data(for example mandatory data for business central like Business Posting Group) and start the send process towards Microsoft Dynamics 365 Business Central. First we check if the order already exists, if it exists we throw an error and skip the order. If it does not exists we check if the customer exists and depending on the outcome create or update the customer. We check if all products exist and then we commit the order.

We differentiate in creating the customer based upon the source data we receive. if we receive from the source a company name we will create a company debtor with the underlying contact. If we receive no company name we will receive a person debtor.

We check if the customer exists per default by email address.

Ordertypes

You can determine what type of order you want to send towards Microsoft Dynamics 365 Business Central.

Our Business Central integrations supports Orders or Invoices.

Settings

Within APIcenter you can set specific settings that are mandatory for Microsoft Business Central, like Customer Posting Group, General Business Posting Group etc. For a complete overview please check the documentation.

Standard we offer functionality to make specific mappings like payment terms and methods from the LightspeedPos to the Microsoft Dynamics 365 Business Central.

Do you want to make use of a default debtor? This is also per default available in APIcenter.

Datamapper

Per default we supply a mapping that makes sure you can send an order towards Microsoft Dynamics 365 Business Central. You can also make adjustments to this yourself. If you make a mistake you can always go back to default.

Default values that are mapped are for example:

• Customer Name
• Billing address street
• Number
• Postalcode
• City
• Country
• Shipping address street
• Number
• Postalcode
• City
• Country
• SKU
• Quantity
• Price

Process

Products are synced from Microsoft Dynamics 365 Business Central to LightspeedPos. Within this sync we can send different types of product. We gather our data from Microsoft Dynamics 365 Business Central based upon the last modified date, then we run it through our APIcenter to have the correct settings, values and formats before we send it to the LightspeedPos. Once we start the send side we first check if the products exists, if it does not exist we create it otherwise we update the article. The linkin pin is the article number, sku.

You can differentiate within APIcenter the behaviour between creating and updating products. For example when we create a product we send in the long description from the Microsoft Dynamics 365 Business Central, but if you enriched the data after this in LightspeedPos you don't want to have it overwritten with an update for this you can use

the settings that are related to the product update.

Product Types

Basically we support simple, virtual, variant/configurable products.

Publish Products

You can determine via a setting in APIcenter if newly created products should be published immediately or if they are created in a draft status so you can enrich them first in the LightspeedPos before publishing.

Attributes/Features

Besides the generic and custom added fields from Microsoft Dynamics 365 Business Central we also support Item Attributes from Microsoft Dynamics 365 Business Central. These needs to be manually mapped in APIcenter via the Attributes or the Features mapping tables.

Attributes are used for creating configurable products, like size/color/options. Features are used as extra information fields, think about country of origin, type, delivery time etc.

Categories

Categories are supported

Images

Images are supported from Microsoft Dynamics 365 Business Central to LightspeedPos. Please be aware that Microsoft Dynamics 365 Business Central only supports 1 image. When you add multiple images in your store you are advised to turn of the image functionality on update.

Datamapper

You can map the fields that are available in the API. For a default working integrations we already mapped the basic fields that are needed; for example

SKU

• Name/Title
• Long Description
• Short Description
• Price excl. tax or incl. tax
• Quantity
• EAN/GTIN
• Currency