To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Signing off Data Dictionary ,
Agreeing on the user primary identifier. PS: Please note that any non-PI identifier should be available in all the channels (Email & SMS & Whatsapp & App Push) you intent or potentially intent to run on Replen.it
Required User Attributes List Sign Off (Identifier, Opt-in Status…)
Required Purchase Event and Parameters Sign Off (Currency, Price, Quantity, SKU, Time Stamp..)
Required Product Attributes List Sign Off (Name & URL & SKU & Image…)
Completing Transaction Data Ingestion via Replen.it Upsert API ,
Sign off the API triggering events (Purchase & Return & Not Delivered…) ,
Sign off the Replen.it Historical API payload Scheme and Fields , ,
Client to set-up the Replen.it Upsert API connection for the historical transactional data with required fields (To the API endpoint shared during Pre Integration Phase)
Engineering to confirm the API connection stability , table format and triggering events
Completing User Data(Attributes) Ingestion via Replen.it Upsert API,
Sign off the API triggering events (User Added, Opt-in Status Updated, User Removed…) ,
Sign of the Replen.it User API payload Scheme and Fields , ,
Client to set-up the Replen.it Upsert API connection for the user data with required fields (To the API endpoint shared during Pre Integration Phase
Replenit to confirm the API connection stability , table format and triggering events
Completing Product Data (Attributes) Ingestion via the decided methodology (CSV or API),
Product feed as a CSV File
Product feed via Product Catalog API ,
Sign off the Triggering Frequency (Daily, 12 hours interval etc.) and Events for Product Catalog API (Product Added, Product Removed, Attribute Changes),
Sign off the Product Catalog API Payloads and Fields , ,
Client to set-up the Replen.it Product Catalog API connection for the product data with required fields (To the API endpoint shared during Pre Integration Phase
Replenit to confirm the API connection stability, table format and triggering events
Client Level QA from the Data Integrity and API health-score page at the platform ,
Signing of the Replenishment Algorithm for SKU and User Level duration calculation, ,
Run the model for SKU level replenishment duration for every SKU,
Run the model for User level replenishment duration for every User,
