Authorized Seller Integration Data Use

Small Batch Direct 3PL connects seller-authorized sales channels only as part of our contracted warehouse, fulfillment, inventory, shipment tracking, support, and billing services. Integrations are not offered as standalone public software, data products, advertising tools, or marketplace account-management services.

Authorization Model

• Sellers must own or be authorized to connect each store, seller account, marketplace account, or sales channel.
• Where supported, sellers authorize access through OAuth, PKCE, or another platform-approved authorization flow.
• We do not ask sellers for marketplace passwords, shared staff logins, or credentials that bypass the platform authorization process.
• Authorization tokens and credentials are used only to operate the connected seller's fulfillment and inventory workflows.

Data We Request

We request only the information needed to receive, store, pick, pack, ship, track, support, bill, and reconcile the seller's orders and inventory.

• Seller account, shop, storefront, or integration identifiers and configuration.
• Paid order identifiers, order status, order timestamps, line items, SKUs, listing or product identifiers, quantities, shipping method, and order totals needed for warehouse operations.
• Recipient shipping name, shipping address, phone number when available, carrier service, tracking number, and delivery details needed to fulfill orders.
• Shipment confirmation, fulfillment status, tracking events, inventory quantities, SKU matching, and sync logs.
• Technical records needed for security, troubleshooting, auditing, webhook processing, and integration reliability.

Marketplace Email Data

The Etsy connector does not request buyer email access and does not store buyer email addresses for Etsy orders. Seller support and operational communication is handled through Small Batch Direct 3PL account contacts and approved support channels.

Limited Etsy Data Access

The direct Etsy connection does not request Etsy shipping-address access and does not use Etsy as the source of recipient delivery addresses. It is limited to seller-authorized shop and receipt identifiers, sales records needed to bind a receipt to the correct seller, exact-SKU listing inventory, and carrier/tracking updates for an already-bound receipt.

The first Etsy integration phase does not create portal orders from Etsy receipts. Planned Shippo order intake will be a separate seller-authorized connection and will not be activated until its setup, permissions, data handling, and client controls are completed and disclosed.

How We Use Integration Data

• Import authorized seller orders into the 3PL portal for fulfillment.
• Match order lines to warehouse SKUs, inventory, receiving records, lots, and shipping workflows.
• Create shipments, update fulfillment status, post carrier and tracking information, and support returns or order exceptions.
• Sync exact-SKU inventory counts back to connected channels when the seller enables inventory sync.
• Provide seller support, billing records, audit trails, security review, and operational troubleshooting.

What We Do Not Do

• We do not scrape marketplaces, use browser automation to extract protected marketplace data, or bypass platform access controls.
• We do not sell, rent, broker, sublicense, or resell seller data, buyer shipping data, API access, authorization tokens, or marketplace-derived data.
• We do not use seller or marketplace data for unrelated advertising, retargeting, competitor analysis, data enrichment, or public data products.
• We do not use connected-channel data to train artificial intelligence or machine learning models.
• We do not divert checkout, replace marketplace purchase flows, or contact buyers outside the fulfillment and delivery context authorized by the seller and platform rules.

Retention, Deletion, and Security

We retain integration data only as needed for fulfillment, inventory, shipment tracking, support, billing, tax, accounting, audit, legal, contractual, security, and operational purposes. When a seller disconnects an integration or ends service, we delete, return, or de-identify seller and customer delivery data when no longer needed, subject to required retention, dispute resolution, and normal backup purge cycles.

We use administrative, technical, and operational safeguards designed to protect integration data, including HTTPS/TLS, role-based access, access limitation by business need, credential restrictions, security monitoring, and incident escalation.

Support and Data Requests

Sellers, customers, and platform partners can contact us for integration support, disconnection help, access questions, correction requests, or deletion requests. We may coordinate requests with the applicable seller or platform when we process data on their behalf.

Related Policies

See our Privacy Policy and Terms of Service for additional service, privacy, retention, billing, and legal terms.

Contact Us