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
  • Automations
  • File Clean Up

Was this helpful?

Export as PDF
  1. Customers

Settings

Automations

Data Sync

Data sync automation provides a greater flexibility in controlling the data sync from the app to Klaviyo. Merchants now have the ability to control when the data is synchronised to Klaviyo.

  • Enabling data sync will allow data to be synced automatically to Klaviyo after file import is completed.

  • Disabling data sync will not allow data to be synced automatically to Klaviyo after file import. However, data will still live on the app (marked as Pending) and you can manually do a sync at a time that suits your needs.

File Cleanup

An automated task that runs once a day which scans all processed files to check if any need to be deleted. The check for deletion is based on the configured file cleanup threshold.

  • Enable - will allow the task to run once a day

  • Disable - the task will not run and no files will be deleted even if file cleanup threshold is configured.

File Clean Up

To ensure efficient management of storage resources, cleanup process will help maintain a clean and organised storage environment after file import process. Merchant can configure the number of days to keep processed files before it is automatically deleted.

The file cleanup logic is as follows:

  • For example, a file is uploaded and processed on July 10th

  • Retention days is set to 30 days

  • Then, the processed file will be automatically deleted on July 15th

PreviousMappingsNextSupport

Last updated 1 year ago

Was this helpful?