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
  • Supported features
  • Connection
  • Products
  • Orders
  • Mappings

Was this helpful?

Export as PDF
  1. Core
  2. Settings

Harmony Integration with DotApparel

PreviousNotificationsNextModules

Last updated 3 months ago

Was this helpful?

Supported features

The following features are currently supported by DotApparel Core

  • Products

  • Inventory

  • Orders

  • Fulfillments

  • Marketplace

  • Images (via S3/Cloudinary. No native image integration from Harmony)

  • Customers

Coming soon

  • Gift Cards

  • Refunds

Connection

A keyword should be configured along with URL, username and password. These should be available in the reference sheet, otherwise can be retrieved from merchant/FBS team.

Products

Harmony price fields settings are used to determine which field should we use for original/markdown price from Harmony response.

Orders

Freight options

  • Carrier code: Determines which carrier the order should be shipped with (i.e. Aus Post, StarTrack, etc.)

  • Freight stock item namekey: This is configured in Harmony by FBS & merchant and is required as part of the order payload. This should be available in Reference sheet or can otherwise be retrieve from FBS/merchant.

Click & Collect orders:

However, Harmony requires shipping address field to be populated in order payload so we also need to add a dummy value for this via order mapping.

Harmony specific values

These are constant values that should be readily configured for each brand, and are required as part of order payload. These should be available in reference sheet or can otherwise be retrieved from FBS.

  • Agent zone

  • Originated warehouse

  • Payment merchant ID

  • Payment card type

  • Shop debtor

These make sure that order placed via marketplace can be processed against different payment information and fulfilled by different warehouse within Harmony.

Mappings

Most of the mappings are similar to what’s currently available to Apparel21. However there are a few areas that are specific to Harmony:

Orders

  • By default, Harmony uses capitalisation for all order information (names, addresses, etc.)

  • altOrderNumber: alternative order number mapping, only used for marketplace order.

Current implementation also enable C&C order posting. If merchant enables new pick up location it they need to inform us to update the settings:

Fulfillment warehouse will be overridden for click and collect order (Local pickup), which will use the warehouse namekey that’s configured in the settings

Marketplace order can also override these fixed values, specifically:

Example mapping (only for address1 but can update for other fields if required)