> ## Documentation Index > Fetch the complete documentation index at: https://parabola.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Connect Deposco to Parabola > Pull Deposco inventory, orders, shipments, and receipts into Parabola to automate fulfillment reporting, sales-channel reconciliation, and warehouse alerts. Deposco is a cloud-based warehouse management system (WMS) and order-management platform built for fast-growing ecommerce brands, DTC companies, 3PLs, and retailers. Connecting Deposco to Parabola lets ops, finance, and supply-chain teams pull inventory, order, shipment, and receipt data into the same flows they use for sales-channel reconciliation, carrier audits, and BI reporting, without writing code. ## Pull from Deposco The **Pull from Deposco** step brings live data from your Deposco environment into Parabola so you can transform it, blend it with data from other systems, and trigger alerts on custom logic. ## How to authenticate Deposco uses **OAuth 2.0** for API access. You'll create an application in the Deposco Developer Portal, install it in your environment, and connect Parabola using the resulting credentials. * Log in to the [Deposco Developer Portal](https://developer.deposco.com/). * Navigate to **Applications** and click **Create Application**. * Complete the application form, including the access scopes you need. Since this step pulls data only, you only need **Read** access. * Submit your application for Deposco review and approval. * Once approved, you'll receive a **Client ID** and **Client Secret** on the application's detail page. * After approval, use the installation link provided in the Developer Portal. * A user with admin access to your Deposco environment must open the link, log in, and grant access to the application. * This generates a **Refresh Token** for your application. * In your Parabola flow, add a **Pull from Deposco** step. * Click **Authorize** and enter your **Client ID**, **Client Secret**, and **Refresh Token**. * Pick the Deposco resource you want to pull and configure any filters. ## Available data The Pull from Deposco step gives you access to a wide range of warehouse and supply-chain records: * **Inventory items and adjustments**: SKUs, descriptions, dimensions, weights, pricing, UPCs, and item-tracking settings. Filter by facility, location, lot number, serial number, and inventory condition. * **Orders**: Outbound fulfillment orders with customer details, line items, status, and fulfillment dates. Includes: * **Customer orders** (B2C and B2B) managed through Deposco's order-management system. * **Purchase orders**: Inbound orders from suppliers with vendor details, line items, and expected receipt dates. * **Transfer orders**: Inbound and outbound transfers between facilities with shipment tracking. * **Returns**: Return merchandise authorizations (RMAs) with reasons and disposition, and returns to suppliers with order and shipment details. * **Outbound shipments**: Shipped orders with tracking numbers, carrier details, packages, costs, and delivery status. * **Receipts**: Received quantities for purchase orders and inbound shipments by item, lot, and location. * **Warehouse operations**: Facilities (warehouse and DC details including addresses, contacts, and operational settings) and locations (storage areas within facilities with zone assignments and storage details). ## Common use cases * **Reconcile orders across sales channels**: Join Deposco orders with [Shopify](/product/integration/shopify), [Amazon Seller Central](/product/integration/amazon-seller-central), or [Walmart](/product/integration/walmart) to flag missing orders or status mismatches before customers notice. * **Audit carrier invoices**: Cross-reference Deposco shipment costs against bills from [DHL](/product/integration/dhl), [FedEx](/product/integration/fedex), [UPS](/product/integration/ups), or [EasyPost](/product/integration/easypost) to catch overcharges and billing errors. * **Send fulfillment data to accounting**: Push Deposco shipment and order data into [NetSuite](/product/integration/netsuite) or [QuickBooks Online](/product/integration/quickbooks-online) for clean revenue and fulfillment-cost reporting. * **Validate receipts against POs**: Compare Deposco receipts to purchase orders from your ERP (such as [Fulfil](/product/integration/fulfil) or [Cin7](/product/integration/cin7)) to catch short-receipts and quantity mismatches. * **Trigger inventory and SLA alerts**: Send a [Slack](/product/integration/slack) message when inventory drops below reorder thresholds, when receipts don't match expected quantities, or when orders miss their planned ship date. * **Build cross-functional dashboards**: Export reconciled Deposco data to [Google Drive](/product/integration/google-drive), [Smartsheet](/product/integration/smartsheet), [Snowflake](/product/integration/snowflake), or [BigQuery](/product/integration/bigquery) so ops, finance, and CX work from the same numbers. ## Tips for using Parabola with Deposco * **Match cadence to use case.** Hourly during peak fulfillment for active monitoring, nightly for inventory reconciliation, weekly for performance reports and supplier reviews. * **Pull incrementally.** Filter on order date or last-updated so each run only handles new or changed records. * **Combine inventory with order lines.** Joining current stock against open orders surfaces what's selling vs. sitting and helps pace replenishment. * **Card up complex flows.** Group related steps into cards with notes so the next person can audit transformations and custom rules without guessing. * **Watch facility filters.** When working multi-warehouse, filter early by facility to keep payloads focused and dashboards clear. * **Archive history for trends.** Send reconciled Deposco data to a warehouse on a regular cadence so you can analyze trends without hitting the API repeatedly. ## FAQ ### Can I push data back into Deposco? The Pull from Deposco step is read-only. To write back to Deposco (for example, creating an order or updating inventory), request a Deposco application with **Write** scopes and use a generic **Send to an API** step with your access token. ### Does Parabola support Deposco webhooks? The native step is API-pull only. For closer-to-real-time updates, schedule your flow on a tight cadence (every 15 to 30 minutes) or trigger Parabola via [Parabola's webhook trigger](/product/integration/webhook) from a service that receives Deposco events. ### What scopes should I request when creating my application? Only the scopes you need. For Parabola pull flows, **Read** access on the resources you plan to use (orders, inventory, shipments, receipts) is enough. Add scopes later if you expand what the flow does. ### Can I pull from multiple Deposco environments? Yes. Add multiple Pull from Deposco steps and authorize each with separate Client ID, Client Secret, and Refresh Token values, then union the results downstream. *** With Deposco and Parabola connected, the carrier audits, inventory reconciliations, and SLA reports your team rebuilds every week run on a schedule, with exceptions landing in the systems where ops, finance, and CX already work.