Integration Specifications
This page will help you learn about how Daasity replicates data from Extensiv (Skubana), the limitations of the data we can extract, and where the data is stored in the Extensiv (Skubana) schema.
Integration Overview
Seamlessly Integrate Your Products, Fulfillment Centers & Sales Channels In One Platform. Extensiv (Skubana) is an order management platform that helps brands, merchants and 3PLs intelligently manage orders.
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
Growth
API Endpoints
The Daasity Extensiv (Skubana) extractor is built based on this Skubana API documentation. The following endpoints are used by Daasity to replicate data from Extensiv (Skubana:)
The Orders endpoint runs each hour and all other endpoints are updated daily.
Limitation: due to the impact on Extensiv (Skubana), for merchants with a large number of products, the Product Stock Totals endpoint will be used in lieu of the Inventory endpoint to ensure that the API will return data in a timely manner
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Skubana integration illustrating the different tables and keys to join across tables.
Extensiv (Skubana) Schema
The Daasity Extensiv (Skubana) 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.
FBA Inventory Levels
Endpoint: Retrieve FBA inventory
Update method: UPSERT
Table Name: [
skubana.fba_inventory_levels]
Inventory Levels
Endpoint: Inventory or Product Stock Totals depending on the volume of SKUs
Update method: UPSERT
Table Name: [
skubana.inventory_levels]
NOTE: Daasity cycles through each warehouse to retrieve the inventory data
For merchants with a large volume of SKUs the Inventory endpoint is not performant as Skubana has to do calculations to determine the on hand quantity. If you have a large number of SKUs we will use the Product Stock Totals endpoint instead but populate the same table
Listing SKU
Endpoint: Product Listing
Update method: UPSERT
Table Name: [
skubana.listing_sku]
Order Items
Endpoint: Orders
Update method: UPSERT
Table Name: [
skubana.order_items]
Orders
Endpoint: Orders
Update method: UPSERT
Table Name: [
skubana.orders]
Purchase Order Items
Endpoint: Purchase Orders
Update method: UPSERT
Table Name: [
skubana.purchase_order_items]
Purchase Orders
Endpoint: Purchase Orders
Update method: UPSERT
Table Name: [
skubana.purchase_orders]
Related Orders
Endpoint: Orders
Update method: UPSERT
Table Name: [
skubana.related_orders]
Sales Channels
Endpoint: Sales Channels
Update method: UPSERT
Table Name: [
skubana.sales_channels]
Shipment Carrier Services
Endpoint: Shipment Providers
Update method: UPSERT
Table Name: [
skubana.shipment_carrier_services]
Shipment Carriers
Endpoint: Shipment Providers
Update method: UPSERT
Table Name: [
skubana.shipment_carriers]
Shipment Package Types
Endpoint: Shipment Providers
Update method: UPSERT
Table Name: [
skubana.shipment_package_types]
Shipments
Endpoint: Shipments
Update method: UPSERT
Table Name: [
skubana.shipments]
SKU Attributes
Endpoint: Products
Update method: UPSERT
Table Name: [
skubana.sku_attributes]
SKU Components
Endpoint: Products
Update method: UPSERT
Table Name: [
skubana.sku_components]
SKU Labels
Endpoint: Products
Update method: UPSERT
Table Name: [
skubana.sku_labels]
SKUs
Endpoint: Products
Update method: UPSERT
Table Name: [
skubana.skus]
Vendors
Endpoint: Vendors
Update method: UPSERT
Table Name: [
skubana.vendors]
Warehouses
Endpoint: Warehouses
Update method: UPSERT
Table Name: [
skubana.warehouses]
Last updated