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.
Key Topics
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
- Inventory Planner Schema
- Related Resources
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:
- 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
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)
The embedded diagram houses the ERD for the Daasity Inventory Planner integration illustrating the different tables and keys to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.
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
| JSON Element | Database Column |
| purchase_order::id | purchase_order_id |
| purchase_order::reference | purchase_order_number |
| purchase_order::status | status |
| purchase_order::source | source |
| purchase_order::type | type |
| purchase_order::vendor | vendor |
| purchase_order::last_modified | last_modified |
| purchase_order::total_ordered | total_ordered |
| purchase_order::total_received | total_received |
| purchase_order::created_date | created_date |
| purchase_order::received_date | received_date |
| purchase_order::expected_date | expected_date |
| purchase_order::created_at | created_at |
| purchase_order::updated_at | updated_at |
| purchase_order::warehouse | warehouse |
| purchase_order::warehouse_display_name | warehouse_display_name |
| purchase_order::vendor_display_name | vendor_name |
| purchase_order::source_display_name | source_name |
| purchase_order::replenishment_type | replenishment_type |
| Daasity: account_id | _account_id |
| Daasity: timestamp when loaded into DB | __synced_at |
Purchase Order Items
- Endpoint: Purchase Orders
- Update Method: UPSERT
- Table Name: inventory_planner.purchase_order_items
| JSON Element | Database Column |
| MD5(purchase_order::id + purchase_order::item::id) | key |
| purchase_order::id | purchase_order_id |
| purchase_order::item:id | purchase_order_item_id |
| purchase_order::item:sku | sku |
| purchase_order::item:title | title |
| purchase_order::item:vendor_reference | vendor_reference |
| purchase_order::item:vendor_name | vendor_name |
| purchase_order::item:replenishment | replenishment |
| purchase_order::item:cost_price | cost_price |
| purchase_order::item:received | received |
| Daasity: account_id | _account_id |
| Daasity: timestamp when loaded into DB | __synced_at |
Related Resources