Integration Specifications

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

Integration Overview

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.

Integration Availability

This integration is available for:

• Enterprise

API Endpoints

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:

• Variants

Entity Relationship Diagram (ERD)

Click here to view the ERD for the Daasity Back In Stock integration illustrating the different tables and keys to join across tables.

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.

• Notifications

Notifications

• Endpoint: Variants

• Update Method: UPSERT

• Table Name: [back_in_stock.notifications]

JSON Element	Database Column
sku, limit: 64	sku
product_id	product_id
variant_no	variant_no
description, limit: 255	description
unsent_notifications_count	unsent_notifications_count
sent_notifications_count	sent_notifications_count
notifications_count	notifications_count
notification_last_added_at	notification_last_added_at
unit_price	unit_price
Daasity: source_id	__source_id
Daasity: account_id	_account_id
Daasity: MD5(sku + product_id + variant_no)	__sync_key
Daasity: timestamp when loaded into DB	__synced_at