This operation connects to Doba using API-based credentials (Retailer ID, optional Tag, and Email). Once authenticated, it pulls the primary inventory feed, creating or updating products in your system. You can map fields such as SKU, Name, Brand, Category, MPN, and other basic product details to match your catalog structure.

Key Points

• Daily Sync: Fetches new and existing SKUs to keep your catalog updated.
• One Product per SKU: Avoids duplicates by treating each SKU as a unique product.
• Mapping Template: Use the built-in template to map Doba’s fields (e.g., “Brand” → “Brand Name” in your system).
• Parent/Child Items: Items can be arranged as parent/child if the feed supports variants (e.g., color or size).
• No Manual Credentials: Doba sends an authorization link to the specified email; users must log in to grant access.

When to Use
Choose this feed for your core product data, pricing, names, categories, and essential product attributes.

This secondary operation also connects to Doba via the same API-based credentials but pulls an additional or alternative inventory feed. It often includes fields not found in the primary feed or updated data for specific SKUs.

Key Points

• Supplemental Data: May include extra attributes like extended descriptions, alternate images, or secondary SKUs.
• Similar Setup: Uses the same Retailer ID, optional Tag, and Email for authentication.
• Field Mapping: A separate mapping template may be provided, letting you link these supplemental fields to your existing product records.
• Combine with Primary: Use both feeds together for a more complete product catalog.

When to Use
Ideal for enhancing product information or if you need specialized data beyond what the primary feed provides.

This operation sends order details to Doba so they can fulfill them on your behalf. You’ll provide the shipping address, items (SKUs, quantities, etc.), and other relevant order data. Doba processes these orders once the request is received.

Key Points

Authentication & Connection

• Uses the same Retailer ID, optional Tag, and Email to authenticate.
• After login, Doba authorizes your system to send order data on behalf of the customer.

Order Fields

• Fulfillment Request: Includes details like request key, ID, and status.
• Line Items: Each product’s SKU, quantity, cost, and other item-level data.
• Shipping Address: Name, address lines, city, state/province, postal code, country, and phone.
• Totals: Estimated dropship fees, shipping costs, and subtotal amounts.

Mapping Template

• Doba exposes specific fields for the fulfillment request and item lines.
• Map these fields to your order data to ensure accurate submission.

Process Flow

• You create an order in your system.
• The order is sent to Doba via this operation.
• Doba confirms receipt and processes the request if everything is valid.

When to Use
Whenever you need Doba to handle shipping and fulfillment for orders placed in your store.

Once Doba has processed and shipped an order, this operation retrieves shipment details. It helps you track each order’s progress and update your customers with accurate shipping information.

Key Points

• Waybill/Tracking Number: Returns the shipment’s tracking ID, which you can share with customers.
• API-Based Connection: Uses the same Retailer ID, Tag, and Email to pull shipment updates from Doba.
• Mapping Template: You can map fields like carrier, tracking URL, and shipping status back into your system.
• Order Status Updates: Once shipment data is received, you can automatically mark orders as shipped and notify customers.

When to Use
Run this operation after sending fulfillment requests to see which orders have shipped, their tracking info, and any status updates.