Syncing Data

Overview

This explains how retailers provide data files for feeding information of products, orders and customers to Citrus. First, the data structures and the formats of each type of data will be represented. Then, the protocols and constraints for system integration between Citrus and retailers will be described.

Introduction

In order to generate Ads, Citrus needs product, customer, and order data from retailers. The data needs to be populated by the retailer, then it is stored, processed, and updated in the system of Citrus. To automate the process of downloading and updating the data, both Citrus and each retailer need to agree on the format and structure of the data, as well as the protocol for the communication between the retailer's and Citrus systems. This documentation describes in detail the specifications for the constraints on the feeding of three types of data: product, customer, and order data.

Syncing Options

Depending on your integration requirements you may wish to sync your data via our API, or by syncing files. Citrus supports both types of syncing, please see the respective pages within the "Syncing Catalog", "Syncing Customer Data", and "Syncing Order Data" pages.

Syncing Data Via File Protocols

There are additional protocols and practices that need to be adhered to when syncing data via file.

Please see "Syncing Data Via File Protocols" for more information