User Guide
  • Intro
    • Welcome
      • About DotApparel
      • What is DotApparel?
      • Where is it hosted?
      • What platform(s) do we support?
      • How does syncing work?
      • Solution architecture
      • Definition of “Instance”
      • Security Overview
    • Implementation
      • Google Cloud and Firebase
  • Quick Links
  • Core
    • Overview
    • Dashboard
    • Orders
      • Mappings
      • Integrations
    • Returns
      • Mappings
    • Products
      • Mappings
        • Default mapping rules
      • Translations
      • Markets
      • Publishing products
    • Inventory
      • Mappings
        • Examples
          • Ignore Sync
          • Inventory Buffer
          • Keep Items Sold Out
          • Unlimited Inventory
    • Customers
    • Rewards
    • System Alerts
    • Settings
      • Shopify Locations, DotApparel Locations and Inventory Buffers
      • ERP credentials
      • Product images
      • Fulfillments
      • Payment gateways
      • Gift cards
      • Refunds
      • Notifications
      • Harmony Integration with DotApparel
    • Modules
      • Ship From Store
      • Local Pickup/Click & Collect
      • Shopify Markets
      • Returns
        • Australia Post (AusPost)
        • Loop Returns
      • Auto-Refunds
        • Refunding Shopify Orders from POS (In-Store)
      • Integrate with Brauz (app)
      • Integrate with The Wishlist (app)
    • Release Notes
    • Troubleshooting
      • FAQs
      • How to raise a support ticket for an issue
      • Good and bad examples of a problem ticket
      • Want to enable a new omnichannel feature?
      • Want to integrate a marketplace using DotApparel?
  • Customers
    • Overview
      • Email Examples
    • Getting Started
      • Understanding Customer Setup in your ERP
      • Data Sync
      • Configuration
      • Testing
    • Data Export Approaches
      • Option A: Consultant
      • Option B: In-House
    • Apparel21 Export Templates
    • Apparel21 Export Changelog
    • Dashboard
    • Customers
    • Orders
    • Translations
    • Mappings
    • Settings
    • Support
  • Loyalty
    • Overview
    • Getting Started
      • Terminology
    • Data Sync
      • Workflows
    • Front-End Implementation
    • Rewards Redemption
    • Rewards Emails
    • Things To Know
Powered by GitBook
On this page
  • Adding a New Order Source
  • Dependancy: Integration via Direct API
  • Configuring the order integrations section
  • Example of Qantas Marketplace order configuration

Was this helpful?

Export as PDF
  1. Core
  2. Orders

Integrations

PreviousMappingsNextReturns

Last updated 9 months ago

Was this helpful?

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

  • Identifier source value

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.

  • ERP Freight Option ID - Necessary for posting orders using a fixed freight option.

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.

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.