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
  • May, 2024
  • April, 2024
  • March 23, 2024
  • Feb 8, 2024
  • Jan 25, 2024

Was this helpful?

Export as PDF
  1. Customers

Apparel21 Export Changelog

PreviousApparel21 Export TemplatesNextDashboard

Last updated 1 year ago

Was this helpful?

May, 2024

Sync products between the Klaviyo Catalogue synced for Shopify and Apparel21 data. It involves retrieving Shopify products via API, and matching barcodes.

  • Placed In-Store Order

    • Contains the transaction details and the various products within that

  • Ordered Product

    • Contains only the one product

April, 2024

customers.csv

If privacy is null (not set) set privacy = 0

The privacy field now has three states.

  • 1 = Privacy Ticked / unsubscribe

  • 0 = Privacy unticked (was ticked) / subscribe

  • Null = Privacy never ticked / default is unsubscribe but can be modified to set as "subscribe" depending on the company's privacy policy

March 23, 2024

orders.csv

Conversion of SALE_DATE to ''YYYY-MM-DD"T"HH24:MI:SS+11:00'' format.

The date and time of the transaction will reflect as the date of the event in Klaviyo. The +11:00 at end represents the timezone.

Example: 2018-12-27T12:30:00+011:00

Feb 8, 2024

orders.csv

  • Product REFs

  • Markdown: Y / N

  • Dispatch Store ID + Dispatch Store Name

  • Dispatch Order Number

customers.csv

  • Person REFs

Jan 25, 2024

To ensure smooth syncing to Klaviyo, make sure that all files, especially large ones like bulk files, contain up to 20,000 records or fewer. This will prevent timeouts and syncing issues between DotApparel Customers into Klaviyo.