This article will help you learn about how Daasity replicates data from Back In Stock, limitations to the data we can extract and where the data is stored in the Back In Stock schema.
Click on the links below to take you to the section where you can learn more about this Integration
- Integration Overview
- Integration Availability
- API Endpoints
- Entity Relationship Diagram
- Back In Stock Schema
- Related Resources
Back In Stock is a Shopify app that allows customers to get notified when a product is restocked. It provides merchants with reports on product and email analytics to optimize their inventory, merchandising, and marketing strategies.
This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other.
This integration is available for:
- Pro V2
NOTE: You are considered V2 if...
- Your account says Pro V2 in the Daasity App
Not sure? Reach out to Support@Daasity.com
The Daasity Back In Stock extractor is built based on this Back In Stock API documentation. The following endpoints are used by Daasity to replicate data from Back In Stock:
Entity Relationship Diagram (ERD)
The embedded diagram houses the ERD for the Daasity Back In Stock integration illustrating the different tables and keys to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.
Back In Stock Schema
The Daasity Back In Stock extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.
- Endpoint: Variants
- Update Method: UPSERT
- Table Name: back_in_stock.notifications
|JSON Element||Database Column|
|sku, limit: 64||sku|
|description, limit: 255||description|
|Daasity: MD5(sku + product_id + variant_no)||__sync_key|
|Daasity: timestamp when loaded into DB||__synced_at|