Integration Specifications

This article will help you learn about how Daasity replicates data from Inventory Planner, limitations to the data we can extract and where the data is stored in the Inventory Planner schema

Integration Overview

Inventory Planner is an inventory forecasting and planner software that allows e-commerce companies to optimize inventory purchasing, release cash from overstocked items and capture lost revenue from out-of-stocks.

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 Inventory Planner extractor is built based on this Inventory Planner API documentation. The following endpoint is used by Daasity to replicate data from Inventory Planner:

Entity Relationship Diagram (ERD)

Click here to view the ERD for the Daasity Inventory Planner integration illustrating the different tables and keys to join across tables.

Inventory Planner Schema

The Daasity Inventory Planner 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.

Purchase Orders

  • Endpoint: Purchase Orders

  • Update Method: UPSERT

  • Table Name: [inventory_planner.purchase_orders]

Purchase Order Items

  • Endpoint: Purchase Orders

  • Update Method: UPSERT

  • Table Name: [inventory_planner.purchase_order_items]

Last updated