All pages
Powered by GitBook
1 of 4

Loading...

Loading...

Loading...

Loading...

Mappings

With the DotApparel app, you can control how information from your ERP is displayed in Shopify. This is done through "mappings", which are templates and rules that you can customise. DotDev will set up the initial mappings based on your preferences, but you can always make changes yourself within the app.

Orders

This section shows all orders that have been placed online. Each line item represents an order.

Next to each order, you’ll see the sync status and the fulfilment status. "Posted" means that the order has been successfully synced to ERP.

There are three fulfilment statuses, and these statuses are automatically updated as soon as the next sync run has been completed. This fulfilment sync runs every hour.

  • Unfulfilled

  • Fulfilled

  • Partially fulfilled

View more details about the order

You can click on each line item to display the data associated with each order. On the left, is Shopify data. On the right, is ERP Request data which is the data that is sent through to ERP from Shopify.

This data is very useful for debugging any order issues with ERP. They'll usually ask for an "Order Payload" in which case, you can simply copy this yourself by clicking Show XML in the ERP request XML section.

Fraud Solution

Shopify offers a built-in feature which will be utilised for this integration. When Shopify captures an order, it assigns a level of "risk" to the order which indicates whether further investigation should be made before dispatching the goods.

Shopify will be configured such that payments are not captured by default, only authorised. A will be created such that when an order fraud risk is acceptable, the payment will be automatically captured.

If the order risk is unacceptable, the payment will remain in an authorized state, the order will be tagged with a fraud tag and an email sent to the store email address. A saved search will be set up in the Shopify admin to enable the retail team to easily see these orders.

Only orders which have a captured payment will be synced to ERP.

In the case that an order is erroneously marked as fraudulent, it can be synced simply by capturing the payment in the Shopify admin, which will trigger a fresh webhook to the integration.

Shopify flow workflow

The following workflow can be used to achieve the above. Remember to update the email address against the "Send email" step.

DotApparel Mapping

Once your fraud flow is set up and tags orders accordingly, you can create a mapping rule in DotApparel to only allow low-medium risk orders to be processed.

DotApparel recommends configuring the flow to apply a “FraudCheck:Pass” tag for low- to medium-risk orders, and then setting up a rule that only allows these tagged orders to proceed.

We don’t block high-risk orders because DotApparel can process orders before the Shopify fraud flow completes, which could result in orders being posted before they are fully checked.

To set this up in DotApparel:

Fraud analysis
Shopify flow
7KB
Fraud workflow.flow
Open

Integrations

This section allows you to configure additional order sources. External apps and marketplaces can be added here which means that DotApparel is helping those orders to flow through to ERP.

Adding a New Order Source

  1. Click on Add New Source.

  2. Select the desired order source from the dropdown menu.

  3. Fill in the required details and apply the appropriate mapping template for these orders.

Dependancy: Integration via Direct API

Some third-party apps and marketplaces offer direct API integration via Shopify, enabling read and write access between Shopify and the platform. Here's an example:

While direct API integration is possible, the execution is managed by the platform provider (The DOM, Qantas Marketplace, etc.) and is not project-managed by the DotApparel team.

DotApparel becomes involved only after the API configuration is complete. At that point, DotApparel will configure the new order source in the app and ensure that orders from the platform are synced to ERP with the necessary order data.

Configuring the order integrations section

Before our team can configure a new order source, our team will need to review a sample order to set up the source identifiers, along with the merchant ID and card type (which are used for other regular orders).

Once our team has configured this, we handover to the merchant for review and confirm that the order is appearing in ERP as expected.

Mandatory

  • Sources - Where the order is from, distinguishing between marketplaces and Shopify orders

  • Label - The name of each config

  • Identifier source field

Most likely needed

  • AP21 Payment Merchant ID

  • AP21 Payment Card Type

Optional based on specific needs

  • Country code - Useful if posting orders using a different country code.

  • Default Email address - Handy if posting orders using a guest email.

  • ERP Person IDX - Useful for posting orders using a guest AP21 person ID.

Example of Qantas Marketplace order configuration

A Shopify tag qantas is automatically to Qantas orders by the Qantas API integration.

In the screenshot above, orders from the Qantas Marketplace are automatically tagged with qantas

Through the qantas tag, DotApparel Core identifies these and then syncs them into ERP, ensuring that the respective Email Address, AP21 Person IDX, Payment Merchant ID, and Payment Card Type are included in the order details.

This process gives merchants the flexibility to enrich order data from third-party platforms, differentiate them in ERP, and achieve accurate reporting.

Identifier source value
ERP Freight Option ID - Necessary for posting orders using a fixed freight option.
This screenshot shows that the Qantas Marketplace integration does the following for the Shopify store: write inventory and orders read inventory and orders read products (Shopify to Qantas)
The Identifier Source Field and Identifier Source Value allow DotApparel to identify orders from the Marketplace source and sync them to ERP according to the configured settings. For example, orders tagged with "Qantas" will be synced to ERP based on the DotApparel app configuration setting.