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
  • How it works
  • Types of Rewards Data and how they sync
  • FAQ for Rewards
  • Rewards product SKU and discount application title

Was this helpful?

Export as PDF
  1. Core

Rewards

PreviousCustomersNextSystem Alerts

Last updated 9 months ago

Was this helpful?

DotApparel can integrate with the Rewards module in ERP, enabling merchants to offer an enhanced shopping experience for their customers. With this integration, customers can easily earn and track loyalty points, view their rewards status, and even make purchases online while earning points towards their rewards.

How it works

DotApparel retrieves rewards account details for a given customer by providing their email address.

If a customer does not already have a rewards account in ERP, the endpoint can automatically create a new account and proceed with it. However, this functionality must be enabled in the app's settings.

Types of Rewards Data and how they sync

  • Customer tier status: DotApparel retrieves the "status" from ERP. DotApparel doesn't calculate the spending, or control the tier rules as that's all handled by ERP.

  • New customers: DotApparel creates a person record for new accounts signed up online.

  • Existing customers: DotApparel attaches online order history to an existing person record.

  • Rewards communications: This is not handled by DotApparel. All should be handled between ERP and the Email Marketing platform.

  • Date for customer rewards account creation: DotApparel only tracks the date for new customers. If an existing customer signs up for rewards at a later stage, DotApparel does not keep track of the date of the account's creation.

FAQ for Rewards

Is it possible to tag a reward profile to allow for rewards-specific marketing whilst the marketing status for all other marketing emails is false?

DotApparel does not handle marketing emails, but it does apply tier tags to customers to enable the email marketing platform to trigger transactional flows. Merchants need to configure the flow and request the email marketing platform to make reward-specific emails "transactional" so that the subscribe status of customers is ignored.

Rewards product SKU and discount application title

It may be necessary for the front-end to locate Shopify rewards products by their SKU number. These products will require discounts to be applied to line items using Shopify Script, and it's important to ensure that both the rewards product SKU and discount application title are consistent with DotApparel.

While both the SKU and title can be customized in DotApparel settings, we suggest using the following conventions:

  • Rewards product SKU: LOYALTY_REWARD

  • Discount application title: Reward Redemption

The Reward product SKU will simply exist in your Shopify product catalogue but will not be active or purchasable on the front-end.