Overview
This integration option gives you full ownership and control over how your data is presented to AGR. It allows you to gather any data you own, transform it as needed and presented to AGR in a way that works best for your business.
This can, for example, be suitable if no standard integration exists for your ERP, or if you need to heavily customize how data is fed to AGR. This is common when you need to apply business logic to the data mapping, or if you need to leverage data from multiple systems, such as your data warehouse, PIM system, or other.
The mapping of your data to the AGR Data Interface can be done either by a 3rd party system integrator or your own IT personnel. AGR offers extensive documentation and technical support to help you get it right.
Note
This integration option covers getting your data from your ERP or alternative data sources into AGR. For exporting data from AGR into your ERP or elsewhere, see the AGR API docs, or Export confirmed orders from AGR.
Data mapping
The AGR Data Interface article describes the database table schema that your data needs to adhere to before it is extracted or loaded into AGR.
Before starting the data mapping, we recommend you download our AGR Data Mapping Template and fill it out to keep track of where each data element in the AGR Data Interface comes from.
Some notes about this template:
Each sheet is associated with a table in AGR.
Each sheet has a description of the role of the table in AGR and it's fields.
You will find two sheets that work as separators, as depicted in the image below.
The sheets to left of the first separator are Core tables to AGR.
The ones in the middle are niche tables that are used only if required.
The ones to the right are exceptional tables that are used for edge cases, e.g. Sales from a Legacy system.
Your AGR onboarding team stands ready to support you in the mapping process, consulting and clarifying the AGR Data Interface to ensure a successful integration.
Data format
AGR stores data in SQL. However, the data can be presented to AGR in either SQL tables or CSV files. Additionally, when presenting your mapped data to AGR, the following requirements apply:
SQL
Table and column names must be identical to the ones listed in the supplied table descriptions.
Table definitions and column data types must match the AGR Data Interface documentation.
CSV
File names must be consistent with the table names provided in the section List of Tables. Naming is case-sensitive.
Headers in the files must be consistent with the column names within each table described in the section List of Tables. Naming is case-sensitive.
Present mapped data to AGR
When your data has been mapped to the AGR Data Interface, you need to grant AGR access to the data, this can be done by either allowing AGR to Extract data from your system or Load data into AGR.
Briefly the options are:
AGR extracts data from your SQL database.
AGR extracts data from your API.
AGR extracts data from your SFTP server using CSV files.
You load data into AGR SFTP server using CSV files.
You load data into AGR via REST API using CSV files.
Check our Grant AGR access to your data article for a detailed explanation on all the options.
AGR daily job
AGR is synced with data from the AGR Data Interface nightly. After the data sync, AGR updates any calculations performed by the system.
The AGR data interface must be updated before the data sync begins to ensure the data presented in AGR is up to date.