Overview
This integration option gives you full ownership and control over how your data is presented to AGR for ingestion via a SQL database connection. 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 pulled into AGR.
Before starting the data mapping, we recommend you download our data mapping documentation template, and fill it out to keep track of where each data element in the AGR Data Interface comes from.
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.
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. To do this, please follow the following steps:
If your database is privately hosted, the integration requires an Integration Runtime service to be installed. See Get data into AGR via Integration Runtime.
Provide AGR’s onboarding team with read access to the SQL database where your mapped data can be found, as described in Grant AGR access to your data.