A practical setup guide for sending fulfillment orders through Order Desk. Configure the integration, map inventory details, and troubleshoot order metadata in one place.
The customer already imports orders from shopping carts into Order Desk.
The customer is building a direct integration from their own system to Dubow.
The customer wants Order Desk rules, folders, metadata, and shipping class matching to control the order flow.
The customer needs full control over the JSON payload and direct endpoint behavior.
The customer prefers a guided app connection with Dubow credentials and configurable defaults.
The customer has development resources and wants to submit orders, status requests, invoice requests, and webhook URLs directly.
Mode switch behavior
The buttons in the header switch the documentation mode. In OrderDesk mode, the API sections are hidden and the navigation changes to OrderDesk setup topics. In Standard API mode, the full Dubow API reference is shown.
ORDERDESK/Start here
Connection Setup
Connect Order Desk to Dubow
Open Order Desk.
Go to Integrations, then Manage Integrations.
Open the Print on Demand tab.
Find and enable Dubow.
Enter the Dubow API credentials provided by Dubow.
Click connect, then configure the integration settings below.
Credential ownership
Dubow creates and provides the integration credentials. Order Desk support cannot retrieve or reset Dubow credentials.
ORDERDESK/Start here
Settings
OrderDesk Integration Settings
Setting
Use
Recommendation
Default Shipping Class
Fallback shipping method when the order does not specify a Dubow-recognized method.
Set a safe default, then configure shipping class matches for specific methods.
Procurement Type
Controls how garment procurement is passed to Dubow.
Use Auto unless Dubow instructs otherwise. Use Inventory or Custom only when all products fit that model.
Default Design Type
Default decoration method for items.
Set the most common method. Override per item with design_type_x when needed.
Third Party Shipping ID
Third-party shipping account Dubow should use.
Only set this after confirming with the Dubow rep.
After Import, Move To
Folder used after Order Desk sends the order to Dubow.
Use a folder that makes successful submission obvious.
After Shipment, Move To
Folder used after Dubow sends shipment details back to Order Desk.
Use a completed or shipped workflow folder.
Default Shipment Return Address
Fallback return address for shipments.
Set a default address. Use Order Desk rules for order-specific return addresses.
ORDERDESK/Start here
Shipping
Shipping Class Match
If shopping cart shipping method names do not match Dubow shipping method names, Dubow will not know which method to use and the default shipping class will be applied. Use Order Desk's shipping class match section to map customer-facing methods to Dubow methods.
Shopping cart method example
Dubow method target
Result
Standard
UPSG or agreed Dubow method
Orders using Standard are sent to Dubow with the mapped method.
Expedited
Agreed expedited Dubow method
Prevents expedited orders from falling back to the default class.
Unmatched method
Default Shipping Class
Fallback method is used for all unmatched orders.
ORDERDESK/Inventory and mapping
Order Data
Preparing Orders for Dubow
OrderDesk sends order-level details through checkout data or order metadata. Item-level details usually come from the matched OrderDesk inventory item metadata and can be supplemented or overridden by variations.
Core concept
The connected store order must carry a SKU that matches the OrderDesk inventory item Code/SKU. That match is what lets OrderDesk pull in the Dubow production metadata saved on the inventory item.
ORDERDESK/Inventory and mapping
Inventory Setup
Inventory Item Setup: How OrderDesk Connects Store SKUs to Dubow Production Data
Customers often expect their connected store to send every production detail to Dubow. In most OrderDesk workflows, the store only sends the item Code/SKU. OrderDesk uses that Code/SKU to find the matching inventory item, then syncs the metadata fields saved on that inventory item into the order item before sending the order to Dubow.
1. Store sends Code/SKU
The connected store sends the ordered item with a SKU such as DEEPBLKK240.
2. OrderDesk matches inventory
The OrderDesk inventory item must use the same value in Code/SKU. If the SKU does not match, the production metadata will not sync to the order item.
3. Metadata supplies Dubow fields
The inventory item metadata tells Dubow the garment SKU, mill, design, colorway, print location, procurement type, and services.
4. Dubow receives the production-ready item
OrderDesk sends the matched item and metadata to Dubow as production instructions for the integration order.
Important
The fields on the left side of the OrderDesk inventory screen, such as Current Stock, Price, Cost, Weight, and Location, are not required for Dubow order submission. The critical value on the left is Code/SKU, because it is what links the store item to the saved metadata fields.
Screen area
What it does
Dubow guidance
Name
Human-readable inventory item name.
Helpful for the customer, but not used as the Dubow product lookup value.
Code/SKU
Inventory matching key used by OrderDesk.
Must match the SKU coming from the connected store. Example: DEEPBLKK240.
Metadata Fields
Name/value fields stored on the inventory item.
This is where Dubow production fields belong, such as print_sku, mill, print_design_id_1, colorway_1, print_location_1, and procurement_type.
Variations
Optional item-level variants such as color, size, or service-related overrides.
Use when the store does not already provide the color, or when a specific item variation needs additional services.
Saving metadata on an OrderDesk inventory item is only the first step. The Dubow fields must also sync into the actual order item before that order is submitted to Dubow.
Store Product SKU
The connected store sends a SKU on the order item, such as DEEPBLKK240.
OrderDesk Order Item SKU
OrderDesk stores that SKU on the imported order item.
Inventory Code/SKU Match
The order item SKU must match an OrderDesk inventory item Code/SKU.
Metadata Sync
OrderDesk syncs saved inventory metadata and variations onto the order item.
Dubow Submission
Dubow receives the synced product, design, colorway, location, procurement, and service fields.
Scenario
Result
Customer action
Store sends DEEPBLKK240 and inventory Code/SKU is DEEPBLKK240.
Metadata can sync into the order item.
Submit after confirming the synced order item includes Dubow fields.
Store sends DEEPBLK-K240 but inventory Code/SKU is DEEPBLKK240.
OrderDesk may not find the inventory item.
Fix the store SKU, create a matching inventory item, or use an OrderDesk rule/mapping.
Store sends no SKU.
Inventory metadata cannot reliably sync.
Make the store send a SKU or use rules to identify and map the item before submission.
SKU changes after launch.
Previously working items can start submitting without Dubow metadata.
Update the OrderDesk inventory item, store SKU, or mapping rule at the same time.
Existing orders are separate
If an order was already imported before the inventory item was fixed, the corrected metadata may not automatically appear on that order item. Resync or re-save the order item before resubmitting.
ORDERDESK/Inventory and mapping
Metadata Mapping
Required Metadata Mapping for Dubow
The metadata fields on the inventory item are the bridge between the customer's store SKU and the Dubow API fields. Use this table to explain what each field controls.
OrderDesk field
Maps to Dubow
When to use
Example
print_sku
IntegrationProduct.ProductName or customer product lookup.
Required for most decorated item setups. This is the product Dubow should decorate, not necessarily the customer's storefront SKU.
K240
mill
IntegrationProduct.Mill
Use when the Dubow product needs a mill/manufacturer to resolve cleanly. Some account-specific setups may use print_mill; use the field name Dubow confirms for the account.
PORT AUTHORITY
procurement_type
IntegrationProduct.ProcurementType
Required when the item needs to specify how product is sourced.
Custom or Contract
print_design_id_1
Designs[0].DesignID
Use for an existing design already in Dubow/DOTS.
7471923
colorway_1
IntegrationColorway.ColorwayID
Use with an existing design when a colorway is required.
9135939
print_location_1
IntegrationColorway.GarmentLocationName
Required for every decoration location.
Left Chest
Do not confuse SKUs
Code/SKU is the OrderDesk inventory matching key. print_sku is the Dubow production SKU/style to decorate. They can be the same, but they do not have to be.
ORDERDESK/Inventory and mapping
Field Sources
Metadata vs Variations vs Order Item Overrides
OrderDesk can receive item details from several places. Customers should understand where a field comes from and which type of setup is best for each value.
Source
Best for
Notes
Inventory item metadata
Permanent Dubow setup fields like print_sku, mill, print_design_id_1, colorway_1, print_location_1, and procurement_type.
Best default for repeated products. This is usually where Dubow production setup should live.
Inventory item variations
Color fallback, size fallback, service choices, or variant-specific overrides.
Useful when the connected store does not send a clean color/size value or when one variant needs a specific service.
Order item metadata
Values imported from the store or synced from inventory into the order.
These values must be present before the order is submitted to Dubow.
Manual order item edits
Emergency correction on one order.
Fixes that order only. It does not repair the inventory item for future orders.
OrderDesk rules
Conditional routing, metadata cleanup, syncing inventory details, holding bad orders, or adding services.
Useful for advanced customers or stores with inconsistent data.
Practical rule
Use inventory metadata for stable Dubow setup, variations for values that change by option, and rules for conditional fixes or review workflows.
ORDERDESK/Inventory and mapping
Variations
Variation Fields: Color Overrides and Services
Variations are useful when the connected store does not already provide enough item detail, or when one item variation needs a different color or service setup than the base inventory item.
Color fallback
If the store does not send a usable color, add a variation such as color = Black so OrderDesk can pass the color to Dubow.
Service override
Add Services as a variation when only certain variants need polybagging, inserts, labels, or other services.
Variant-specific metadata
Use variations when a size, color, or SKU variant needs a different value than the base inventory item metadata.
Variation field
Purpose
Example
color
Supplies garment color when the storefront does not provide it or when the storefront color needs to be standardized.
Black
size
Supplies the item size when the storefront does not provide it cleanly.
XL
Services
Adds Dubow additional services for this item or variation.
Different stores send color, size, and SKU information differently. Decide during setup whether the store SKU already contains everything Dubow needs, or whether OrderDesk should supply missing values through variations, metadata, or rules.
Store behavior
Common issue
Recommended setup
SKU includes product, color, and size.
The store SKU may be good for OrderDesk matching but not the same as Dubow's production SKU.
Use Code/SKU for the store match and print_sku for the Dubow product/style.
SKU only identifies the product.
Color and size may be missing from the Dubow item.
Add color and size as variations or make sure the store sends them as item options.
Store sends Colour instead of color.
The field name may not match the expected setup.
Standardize to the agreed field name or use a rule to copy/normalize the value.
Store sends customer-facing color names.
Customer color names may not match Dubow or vendor names cleanly.
Use color conversion, variation mapping, or agreed color names from the product setup.
Store SKU does not equal Dubow's product code.
Customers may put the storefront SKU into print_sku by mistake.
Use product code matching or metadata mapping so the storefront SKU maps to the correct Dubow print_sku.
Updating an OrderDesk inventory item helps future imports, but it may not automatically repair orders that were already imported. Existing failed orders usually need the corrected inventory details synced onto the order item before resubmission.
Do this before resubmitting
Open the failed order and confirm the order item itself contains the corrected Dubow fields. If not, resync item details from inventory or re-save the order item so the metadata is applied.
Fix the OrderDesk inventory item Code/SKU, metadata fields, and variations.
Open the already-imported OrderDesk order.
Use the available OrderDesk action to sync item details with inventory, or re-save the order item if that is the customer's configured workflow.
Verify the order item now shows required Dubow metadata such as print_sku, mill, print_design_id_1 or print_url_1, print_location_1, and procurement_type.
Resubmit the order to Dubow.
Customer action
What it affects
Edit inventory item metadata
Future orders and any existing orders that are manually resynced.
Edit one order item manually
Only that order item. Future imports are unchanged.
Run a sync inventory details action
Applies current inventory details to selected existing order items.
Fix store SKU
Future imports from the store. Existing imported orders may still need item resync.
ORDERDESK/Order fields
Order Metadata and Checkout Data
Field
Purpose
Notes
ShippingAccount
Third-party shipping account number.
Use only when Dubow should ship on a third-party account.
PackingSlip
URL for the PDF packing slip.
Must be accessible to Dubow.
DateToShip
Requested ship date.
Use Y-m-d format.
DateDropDead
Date the order should reach the customer.
Use Y-m-d format when a firm deadline applies.
First & Last Name
First and last name of recipient.
Name of recipient
Address1
Address field sent to Dubow.
e.g. 123 1st Street North
City
City of recipient
e.g. Saint Cloud
State
State of recipient. Only needed if within United States.
e.g. MN
Postal(Zip)
Zipcode of City
e.g. 56303
Country
Country of recipient.
e.g. US
BulkShip
Flags an order for bulk shipping.
Set to 1 for bulk shipping.
ORDERDESK/Order fields
Metadata Field Reference
These fields can be stored on the OrderDesk inventory item or added to the order item. For repeated artwork fields, replace x with a number from 1 to 8. Example: print_url_2, print_location_2, design_type_2.
Inventory item setup
For most customers, set these once on the OrderDesk inventory item. When the store sends a matching Code/SKU, the metadata syncs into the order item and becomes the production data sent to Dubow.
Field
Purpose
Notes
print_sku
Dubow garment or product style to decorate.
This is not always the same as the storefront SKU or OrderDesk Code/SKU. Order Desk can append color and size. Add * when size and color should not be appended.
print_sku_override
Pass the print SKU as the complete vendor part number.
Set to 1.
print_url_x
Artwork file URL.
Values 1 through 8 accepted. Use print_url when only one design is sent.
print_preview_x
Preview image URL.
Values 1 through 8 accepted. print_preview or image can be used for one preview.
print_location_x
Decoration location.
Required for each design.
print_design_id_x
Dubow Design ID.
Use this instead of print_url_x for existing Dubow designs.
print_design_code_x
Customer design code.
Use when sending a print URL instead of a Design ID.
colorway_x
Colorway ID.
Used for embroidery thread colorways.
design_type_x
Decoration method override.
Use when the item differs from the default design type.
NoDecoration
Flags an undecorated item.
Set to 1.
product_name_field
Controls product identifier type.
Options: ProductName or CustomerProductName.
color
Garment color.
Order Desk attempts to match this to Dubow's color abbreviation list.
size
Garment size.
Used with SKU building and line item sizing.
mill or print_mill
Mill/manufacturer value.
Use the field name confirmed for the customer account. In many Dubow OrderDesk setups, mill is used directly.
procurement_type
Item-level procurement override.
Options: Custom, Contract, Inventory.
Services
Additional services to apply to the item.
Can be saved as item metadata or added as a variation override. Use a comma-separated list when more than one service is needed. Example: Bag2 - Polybag, Insert, Label W/Name.
retail_price
Retail price of the item.
Optional reporting or commercial value.
harmonized_code
HS code.
Useful for cross-border shipping workflows.
ExampleItem services metadata
Services = Bag2 - Polybag, Insert, Label W/Name
ORDERDESK/Order fields
OrderDesk Examples
OrderDesk Metadata Examples
Use these examples when configuring Order Desk item metadata or troubleshooting what Order Desk is sending to Dubow.
Code/SKU: STORE-TEE-BLACK-L
Metadata Fields:
print_sku: 2000
mill: Gildan
print_url_1: https://cdn.example.com/art/customer-logo.png
print_design_code_1: CUSTOMER-LOGO-001
print_location_1: Full Back
design_type_1: Direct to Film
procurement_type: Contract
ORDER DESKOrder metadata
PONumber: OD-10001
SecondaryPO: STORE-ORDER-8891
EndUserPO: CUSTOMER-REF-22
OrderNotes: Rush if possible
OrderStatusNotificationUrl: https://yourdomain.com/webhooks/order-status
Metadata Fields:
print_sku: K240
mill: PORT AUTHORITY
print_design_id_1: 7471923
colorway_1: 9135939
print_location_1: Left Chest
print_design_id_2: 7471924
colorway_2: 9135940
print_location_2: Full Back
procurement_type: Custom
Important
Order Desk sends metadata as name/value fields. Field names should match the labels shown in this section unless Dubow provides account-specific overrides.
ORDERDESK/Artwork and designs
ORDERDESK METADATAArt setup within Order Desk
Artwork and Design Rules
New artwork
Send print_url_x, print_location_x, and optionally print_design_code_x and print_preview_x.
Existing Dubow design
Send print_design_id_x, colorway_x when applicable, and print_location_x.
Multiple designs
Use numbered fields from 1 to 8, keeping each design's URL, location, preview, design ID, design code, colorway, and design type aligned by number.
ORDERDESK/Artwork and designs
ORDERDESK METADATAMatch each numbered design field
Numbered Artwork Fields Must Stay Together
For multi-location or multi-design items, keep each numbered group aligned. Fields ending in _1 describe design slot 1. Fields ending in _2 describe design slot 2.
print_design_id_1 = 7471923
colorway_1 = 9135939
print_location_1 = Left Chest
design_type_1 = Embroidery
print_design_id_2 = 7471924
colorway_2 = 9135940
print_location_2 = Full Back
design_type_2 = Direct to Film
ORDERDESKTwo new artwork files
print_url_1 = https://cdn.example.com/art/left-chest.png
print_design_code_1 = LEFT-CHEST-001
print_location_1 = Left Chest
design_type_1 = Embroidery
print_url_2 = https://cdn.example.com/art/full-back.png
print_design_code_2 = FULL-BACK-001
print_location_2 = Full Back
design_type_2 = Direct to Film
Common mistake
Do not send colorway_2 for print_design_id_1. The numbers must stay aligned for Dubow to apply the correct location and colorway to each design.
ORDERDESK/Artwork and designs
Custom Text and Personalization
Field
Purpose
Format
custom_text_x
Name, number, or other personalized text.
Append 1 through 8 for more than one line.
custom_text_details
Production details for the custom text.
Comma-separated: Font, Color, Position, Width, Height, Notes. Notes are optional.
custom_text_location
Placement for the custom text.
Examples: Full Front, Left Chest, Back.
ExampleCustom text metadata
custom_text_1 = SCHERFENBERG
custom_text_2 = 12
custom_text_details = Block, White, Full Back, 10, 12, Center between shoulders
custom_text_location = Full Back
ORDERDESK/Workflow and support
Workflow
Recommended OrderDesk Workflow
Import the order from the connected shopping cart into Order Desk.
Match each order item SKU to the correct OrderDesk inventory item Code/SKU.
Sync inventory metadata and variations into the order item before submission.
Use rules, product settings, item metadata, and variations to populate Dubow-required production data.
Move orders with missing SKU, artwork, location, procurement, or shipping data to a Needs Review folder.
Confirm shipping class matches before sending live orders.
Send complete orders to Dubow through the enabled Dubow integration.
Move successfully submitted orders into the configured post-import folder.
Receive shipment details back into Order Desk and push tracking back to the shopping cart when configured.
ORDERDESK/Workflow and support
Automation
OrderDesk Rule Examples
Rules can prevent bad orders from reaching Dubow and can fill in missing metadata when the store does not send enough information.
Rule need
Example action
Why it helps
Sync inventory details after import
Run an action to sync order items with inventory details.
Ensures Dubow fields saved on the inventory item appear on the order item before submission.
Add service based on SKU, tag, or product option
Add item metadata Services with values such as Bag2 - Polybag or Insert.
Applies additional services only when needed.
Route blank or undecorated items
Add NoDecoration or move the order to a review folder.
Prevents decorated-item validation errors when no artwork is expected.
Hold missing metadata
Move to Needs Review when print_sku, print_location_1, or artwork fields are missing.
Stops incomplete orders before they generate Dubow API errors.
Move successful submissions
Move to Submitted to Dubow after the Dubow integration action succeeds.
Makes it clear which orders have already been sent.
Recommended workflow
Create a Needs Review folder for orders missing SKU matches, artwork, location, procurement, shipping, or service setup. Submit to Dubow only after required metadata is present on the order item.
ORDERDESK/Workflow and support
OrderDesk Preflight Checklist
Check
Why it matters
☐
Dubow credentials are connected.
Required before any order can be sent to Dubow.
☐
Default shipping class is set.
Used when a method is not matched.
☐
Shipping class matches are configured.
Prevents all orders from falling back to the default method.
☐
Procurement type is confirmed.
Incorrect procurement values can route products incorrectly.
☐
Store SKU matches the OrderDesk inventory item Code/SKU.
If the SKU does not match, OrderDesk will not sync the saved Dubow metadata into the order item.
☐
Required inventory metadata is saved on the inventory item.
Confirm print_sku, mill, print_design_id_1 or print_url_1, colorway_1 when needed, print_location_1, and procurement_type.
☐
Existing orders were resynced after inventory fixes.
Updating inventory metadata does not automatically fix order items that were imported before the correction.
☐
Numbered artwork fields are aligned.
print_design_id_1, colorway_1, and print_location_1 must describe the same design slot.
☐
Color and size are supplied by the store, variation fields, or rules.
Dubow needs a clean product/color/size combination for production and procurement.
☐
Each decorated item has artwork or design ID and location metadata.
Dubow needs production instructions for each design.
☐
Custom text includes details and location.
Personalization requires both content and production instructions.
ORDERDESK/Workflow and support
OrderDesk Troubleshooting
OrderDesk sends orders into the Dubow API, so many Dubow validation errors can appear in the Order Desk activity log. Use this section to translate those messages into the likely OrderDesk setup or metadata fix.
Common SKU and Metadata Mistakes
Mistake
Symptom
Fix
Store SKU does not match inventory Code/SKU.
Dubow metadata does not appear on the order item.
Fix the store SKU, create a matching inventory item, or use a mapping rule.
Metadata saved on inventory but not synced to the order.
Dubow receives missing print_sku, design, colorway, or location values.
Sync item details into the order item before resubmitting.
print_sku and art URL are swapped.
Product lookup or artwork lookup fails.
Put the product/style in print_sku and artwork URLs in print_url_x.
Field name typo.
Required Dubow value is missing even though the customer thinks it was entered.
Use exact metadata names such as print_sku, print_location_1, and procurement_type.
colorway_1 without print_design_id_1.
Colorway cannot be tied to the correct design.
Keep numbered fields aligned by design slot.
print_location_2 with no print_url_2 or print_design_id_2.
Extra location may not apply correctly.
Use matching numbered fields for every design group.
OrderDesk Setup Checks
Issue
Likely cause
Fix
Wrong shipping method used
Shopping cart method did not match a Dubow method.
Add or correct the shipping class match. The default shipping class is used when no match exists.
Credential connection fails
Credentials are missing, incorrect, or not supplied by Dubow.
Confirm the Dubow username and password supplied for the OrderDesk integration. Do not expose credentials in order metadata.
Artwork missing
Item lacks print_url_x or print_design_id_x.
Add artwork URL metadata or an existing Dubow design ID on the item.
Decoration location missing
Item lacks print_location_x.
Add a valid location for each design.
SKU does not resolve as expected
SKU building appended color and size, or override was not set.
Use print_sku_override, *, or procurement-specific settings as appropriate.
Inventory metadata did not sync into the order
The SKU on the incoming store item did not match the OrderDesk inventory item Code/SKU, or the item was edited after import without syncing inventory details.
Correct the store SKU or OrderDesk inventory Code/SKU, then use OrderDesk's sync item details action on the order item before resubmitting.
Wrong Dubow product was used
The customer assumed Code/SKU and print_sku are the same value.
Set Code/SKU to the store matching value and print_sku to the Dubow production SKU/style.
Color missing or incorrect
The store did not send color, or the color value does not map cleanly.
Add color as a variation field or standardize color values through OrderDesk product settings.
Existing failed order still fails after inventory was fixed
The inventory item was corrected, but the already-imported order item still has the old or missing metadata.
Resync inventory details into the existing order item, then resubmit.
Wrong design or location on a multi-location item
Numbered artwork fields are mixed, such as colorway_2 being paired with print_design_id_1.
Keep _1 fields together, _2 fields together, and so on.
Order submits before setup is complete
No Needs Review workflow exists for missing metadata.
Add rules to hold orders missing SKU, artwork, location, procurement, shipping, or service values.
Additional service not applied
The new Services item metadata is missing or the value does not match a supported Dubow service.
Add Services to the item metadata or variation fields and separate multiple services with commas, for example Bag2 - Polybag, Insert, Label W/Name.
ORDERDESK/Workflow and support
Common Dubow Errors in OrderDesk
Common API errors from OrderDesk submissions, with likely causes and steps to resolve them.
Showing 66 of 66 errors
No errors match your search. Try another term or category.
Auth
Unauthorized. Please check UserID and Password.
What it means
The Authorization block is missing, incorrect, or using credentials
for the wrong environment.
How to fix in OrderDesk
Confirm Authorization.UserID, Authorization.Password,
and whether you are calling sandbox or production.
Auth
Invalid Authorization UserId
What it means
The request user ID is missing, zero, or not recognized.
How to fix in OrderDesk
Use the assigned Dubow API UserID. If using a child customer, the
authenticated user must be allowed to submit for that customer.
Order
Orders list is Empty
What it means
The request did not include any orders in Orders[].
How to fix in OrderDesk
Send at least one order object inside the Orders array.
Order
A PoNumber (Purchase Order Number) was not given.
What it means
The order is missing PoNumber or it is blank.
How to fix in OrderDesk
Send a non-empty, unique PoNumber for every order.
Order
This PO already exists in our system. Duplicate?
What it means
The submitted PoNumber already exists for that customer.
How to fix in OrderDesk
Use a unique PoNumber. For resubmits, use a revision value such as
PO12345-REV1.
Order
Duplicate order. This PONumber already exists.
What it means
Same as duplicate PO. The customer PO has already been accepted or created.
How to fix in OrderDesk
Do not resend the same PO unless directed. Use a new PO value when submitting a
replacement order.
Order
Duplicate PONumber for CustomerID
What it means
Duplicate PO for the submitted CustomerID.
How to fix in OrderDesk
Use a unique PoNumber for the customer.
Order
Is not a valid CustomerID.
What it means
The submitted CustomerID does not exist.
How to fix in OrderDesk
Confirm the customer/company ID with Dubow.
Order
is not a valid child customer
What it means
The authenticated user is not allowed to submit orders for the requested child
customer.
How to fix in OrderDesk
Use the correct child customer or request that Dubow assign access to the
authenticated parent customer.
Order
Customer is in excess of their Credit Limit.
What it means
The account is blocked by a credit limit rule.
How to fix in OrderDesk
Contact Dubow support or accounting before resubmitting.
Order
is not a valid ContactID.
What it means
The submitted ContactID does not exist.
How to fix in OrderDesk
Confirm the contact ID with Dubow.
Order
The Contact's owning Customer is not the specified Customer.
What it means
The contact exists but belongs to a different customer.
How to fix in OrderDesk
Use a ContactID that belongs to the submitted
CustomerID.
Order
Contact is not active.
What it means
The contact exists but is inactive.
How to fix in OrderDesk
Use an active contact assigned to the same customer.
Order
The Order didn't contain any Manifests.
What it means
The order did not include Manifests[].
How to fix in OrderDesk
Add at least one manifest with shipping and line item details.
Payload
Unable to parse payload
What it means
The request body is not valid JSON or the content type is wrong.
How to fix in OrderDesk
Validate the JSON and send Content-Type: application/json.
Payload
One or more required fields are missing or invalid
What it means
A required field is missing, misspelled, or using the wrong type.
How to fix in OrderDesk
Compare your payload with the required examples and field reference.
Shipping
An IntegrationManifest cannot be scheduled to ship on a date earlier than or equal to the day it is placed
What it means
DateToShip is today or in the past.
How to fix in OrderDesk
Use a future valid ship date and account for Dubow turn time rules.
Shipping
An IntegrationManifest cannot have a deadline date earlier or equal to the day it is placed.
What it means
DateDropDead is today or in the past.
How to fix in OrderDesk
Use a future deadline date.
Shipping
Each IntegrationManifest must define at least one LineItems.
Provide the required shipping address fields listed in the shipping section.
Shipping
Address must have at least one of Address1,2,3
What it means
No address line was supplied.
How to fix in OrderDesk
Provide a complete ShipToAddress. Keep using the stricter address
requirements documented above.
Shipping
FedEx ship methods can only be used with a provided 3rd Party Account#.
What it means
The selected FedEx method requires a third-party shipping account.
How to fix in OrderDesk
Set the correct third-party account in the shipping metadata, or change the shipping method mapping to an available option.
Shipping
Ship method '{abbr}' does not support a 3rd Party Account#. Remove the 3rd Party Account# or choose a ship method that supports it.
What it means
The selected shipping method does not allow third-party billing.
How to fix in OrderDesk
Remove the third-party account from the order or update the shipping class mapping to a compatible shipping method.
Product
A ProductName was given without a Mill and no match or multiple was found
What it means
ProductName is ambiguous or not found.
How to fix in OrderDesk
Include Mill, use ProductID, or confirm product
mapping from Lookup Lists.
Product
A ProductName was given without a Mill: Multiple products were found with name
What it means
ProductName and the supplied VendorName matched more than one internal ProductID. A valid vendor name does not guarantee a unique match.
How to fix in OrderDesk
Verify the intended product and resubmit with its Mill or exact ProductID. For example, a lookup for 2000 under S&S Activewear can match multiple records.
Product
A ProductName was given with a Mill and no match or multiple was found
What it means
The product and mill combination did not resolve.
How to fix in OrderDesk
Verify the product style and mill combination in Lookup
Lists.
Product
A VendorProductName was given with a Mill and no match or multiple was found
What it means
The vendor product lookup failed.
How to fix in OrderDesk
Verify VendorProductName and Mill, or use another
supported product lookup path.
Product
An Invalid ProductID was specified
What it means
The submitted ProductID does not exist.
How to fix in OrderDesk
Use a valid Dubow product ID from the product lookup list.
Product
Each IntegrationProduct must unambiguously specify a Product
What it means
Multiple product identifiers resolve to different products.
How to fix in OrderDesk
Use one clear lookup method, or make sure all product fields resolve to the same
part.
Product
Cannot lookup inventory. SKU does not exist or multiple in the system.
What it means
The inventory SKU is missing, inactive, or ambiguous.
How to fix in OrderDesk
Confirm the SKU with Dubow or use a more specific product identifier.
Product
Inventory metadata did not sync
What it means
OrderDesk did not find a matching inventory item from the incoming store SKU, so the saved metadata fields were not copied to the order item.
How to fix in OrderDesk
Make the store SKU match the OrderDesk inventory item Code/SKU, then sync item details with inventory before resubmitting.
Product
print_sku is missing or incorrect
What it means
The item has a store SKU but does not have the Dubow product SKU metadata needed for production.
How to fix in OrderDesk
Add print_sku to the inventory item metadata and confirm mill or print_mill when required.
Product
Not possible to dynamically create an integration product
What it means
The customer is not enabled for dynamic part creation, or required fields are
missing.
How to fix in OrderDesk
Confirm setup with Dubow and include CustomerProductName,
Description, and Color.
Product
[PartNumber] is an inactive part.
What it means
The product exists but is inactive.
How to fix in OrderDesk
Remove the item or contact Dubow to verify availability.
Product
An invalid VendorID was specified: '{vendorId}'
What it means
The vendor identifier is not recognized by Dubow.
How to fix in OrderDesk
Correct the vendor identifier in the outgoing product data, or use a valid VendorName and a unique product reference.
Product
No vendor was found matching VendorName '{name}'
What it means
The supplied VendorName does not match a supplier in Dubow.
How to fix in OrderDesk
Correct the supplier name in the outgoing integration data. Use a recognized VendorName.
Product
Multiple products were found with name '{name}' supplied by {vendor} (ProductIDs: {ids}). Provide a Mill or ProductID to disambiguate
What it means
The product name and supplier match more than one Dubow product.
How to fix in OrderDesk
Correct the product mapping using the exact Dubow ProductID or an appropriate Mill alongside the product name.
Size
Each LineItem must have at least one LineItemSize to define size and quantity.
What it means
The line item is missing LineItemSizes[].
How to fix in OrderDesk
Add at least one size row with quantity.
Size
LineItem for Dubow Owned Inventory Part should not contain more than 1 LineItemSize.
What it means
A Dubow-owned inventory line item has multiple size rows.
How to fix in OrderDesk
Send one size row only or split inventory products into separate line items.
Size
Each LineItemSize must have a quantity greater than 0.
What it means
Quantity is zero, negative, or missing.
How to fix in OrderDesk
Set every LineItemSizes[].Quantity value to a positive integer.
Size
Quantity must be greater than 0
What it means
Quantity is zero, negative, or missing.
How to fix in OrderDesk
Use positive integer quantities.
Size
Each LineItemSize must specify a SizeIndex either in string or integer enumeration.
What it means
The line item size cannot be determined.
How to fix in OrderDesk
Send a valid SizeAsString or SizeIndex.
Size
An unambiguous size cannot be determined for all LineItems.
What it means
The supplied size text cannot be mapped.
How to fix in OrderDesk
Use a supported size format such as XL, 2XLT, or
Medium.
Size
SizeAsString value is not recognized
What it means
The size value is not recognized.
How to fix in OrderDesk
Use a supported size format from the documentation.
Design
No IntegrationDesigns included with LineItem X but NoDecoration does not equal true
What it means
A decorated item is missing Designs[].
How to fix in OrderDesk
Add Designs[], set NoDecoration: true, or use the
inventory workflow.
Design
Missing Design Reference
What it means
The design did not include DesignID,
CustomerDesignCode, DesignCode, or
FilePath.
How to fix in OrderDesk
Provide a valid existing design reference or send a design URL workflow with
DesignTypeName.
Design
Could not use DesignID, DesignCode or CustomerDesignCode...
What it means
No existing design could be resolved and no valid design type was provided for
new art.
How to fix in OrderDesk
Use a valid design reference or include DesignTypeName for new art.
Design
DesignID does not exist.
What it means
The submitted design ID is not valid.
How to fix in OrderDesk
Confirm the design in DOTS or use a valid CustomerDesignCode or
design URL workflow.
Design
DesignID not found or not valid for account
What it means
The design is missing or not assigned to the customer.
How to fix in OrderDesk
Use a valid, customer-authorized DesignID.
Design
Customer does not have rights to DesignID
What it means
The design exists but is not available to the submitted customer.
How to fix in OrderDesk
Use a customer-owned design or request Dubow to assign rights.
Design
Cannot resolve DesignCode
What it means
The submitted design code did not resolve to a design.
How to fix in OrderDesk
Use a valid DesignID, DesignCode,
CustomerDesignCode, or design URL workflow.
Design
DesignTypeName is required
What it means
New art or design resolution needs a decoration type.
How to fix in OrderDesk
Set DesignTypeName in the design block, for example
Embroidery.
Design
There are multiple colorways for this design, but no colorway was provided. Please provide a colorway.
What it means
The design has multiple colorways and none was selected.
How to fix in OrderDesk
Send IntegrationColorway.ColorwayID with the existing
DesignID.
Design
ColorwayID not found or not associated with DesignID
What it means
The colorway is invalid or does not belong to the design.
How to fix in OrderDesk
Verify the ColorwayID belongs to the specified
DesignID.
Design
Incorrect number of thread breaks (Ordinal) called for Design ####. - X of Y Colors Received
What it means
The submitted color ordinals do not match the design's thread breaks.
How to fix in OrderDesk
Update IntegrationColorway.Colors[] ordinals to match the design.
Design
Design #### is an associated design and requires additional locations in "GarmentLocationName" split by a "/" for each location
What it means
An associated design requires multiple locations in order.
How to fix in OrderDesk
Send slash-separated locations such as Full Front/Full Back.
Design
FilePath is not a valid URL
What it means
The art URL is malformed or inaccessible.
How to fix in OrderDesk
Use a properly formatted, publicly accessible https:// link.
Design
Design FilePath and DesignID cannot be used together
What it means
The payload mixes an existing design with new-art submission.
How to fix in OrderDesk
Choose either existing design fields or design URL fields, not both.
Design
CustomerDesignCode already used on another design
What it means
The customer design code is not unique.
How to fix in OrderDesk
Use a unique CustomerDesignCode or reuse the existing design
reference if intended.
Design
Less than 24qty used per colorway for screen print.
What it means
Screen print line quantity is below the minimum.
How to fix in OrderDesk
Increase the quantity to at least 24 units per colorway or use another approved
decoration method.
Services
A service code was provided that is not supported
What it means
The service name/code does not map to a valid service part.
Collect these details before escalating an OrderDesk-to-Dubow issue.
Order Desk order ID and shopping cart order ID.
Dubow customer or program information, if known.
Folder, rule, and integration action used to submit the order.
Order metadata, checkout data, item metadata, and item variations.
Screenshot or export of the OrderDesk inventory item showing Code/SKU and metadata fields.
Shipping method from the shopping cart and the intended Dubow method.
Error response or activity log entry from Order Desk.
ORDERDESK/Additional resources
External Reference
Order Desk Dubow Guide
The official Order Desk guide covers the Dubow connection screen, integration settings, product settings, shipping class matching, and the order and item metadata fields used when sending orders to Dubow.
Everything you need to send orders, work with products and designs, and retrieve status updates. Start with a task or jump directly into the technical reference.
Use this section when you need to build, test, or troubleshoot an integration
order. The detailed field glossary remains available in the Field Glossary topic, but these tools are
designed around the questions customers usually ask during implementation.
Start with a complete request, explore small field-level fragments, or follow a workflow. Every example is illustrative and must be adapted to your customer and design identifiers.
Include the endpoint you were using, your order or PO reference (if relevant), the approximate date and time, and the error message or response. This helps us troubleshoot the request faster.
Do not include API passwords, cloud tokens, or other credentials in your email. Remove unnecessary personal information from examples.
Direct Integration API requests use a valid UserID and Password inside the JSON Authorization block. Credentials are supplied by Dubow IT. Cloud IO Order Creation uses a separate, environment-specific customerToken. See Direct vs Cloud IO before choosing your endpoint.
Warning
Use sandbox credentials only in test. Do not embed production credentials client side or
in public repos.
Unauthorized. Please check UserID and Password.: Happens when credentials
are missing or incorrect.
Make sure Content-Type is set to application/json.
Use test credentials only in sandbox environments; live credentials should be kept
secure.
STANDARD API/Start here
CONNECTIONS AND RELIABILITY
Direct Integration vs Cloud IO
Dubow offers two routes for supported API operations. The Direct Integration API connects to Dubow's systems, while the Cloud IO API provides a cloud entry point. For order submissions, Cloud IO can accept and queue requests when the underlying Integration service is unavailable.
Direct Integration APIintegration.dubowtextile.com
Requests are sent directly to the Integration service.
If the service is unavailable, requests fail. They are not queued; failed requests must be retried by the sending system.
Cloud IO APIio.dubowtextile.com
Order submissions are received through a cloud entry point.
Accepted orders can be queued and automatically forwarded when connectivity to Dubow is restored.
What happens during an outage?
01
Send the order
Submit to the supported Direct or Cloud Order Creation URL, using the correct authentication for that service.
02
If Dubow's Integration service is offline
A Direct request fails and must be retried. An order accepted by Cloud IO is retained for later forwarding.
03
When connectivity returns
Cloud IO automatically forwards queued orders. Confirm that the order was actually created before treating the submission as completed.
Queue acceptance is not final order creation
Automatic queue and resend behavior is documented for Cloud Order Creation. Do not assume pricing, status checks, design creation, or GET lookups are stored for later replay. Do not submit the same PO through both endpoints simply because a Cloud order has not yet appeared in DMS. Check the eventual order result or contact Dubow before retrying an uncertain submission.
Order Creation: production and test URLs
These routes both create orders, but they use different URL structures and Cloud Order Creation has a different authentication requirement.
Authorization.UserID and Authorization.Password in the request body
Uses the standard order JSON generated by the JSON Builder.
Cloud IO
Environment-specific customerToken supplied by Dubow IT
Include the token in the JSON body as customerToken. Confirm the full Cloud request format before switching. Never embed credentials in public or client-side code.
Using Cloud IO as your standard order route
Cloud IO can be used for supported order submissions in normal operation as well as during an Integration service outage. Build and test against the Cloud route and its token requirements before going live. Cloud IO must still be reachable for a submission to be accepted.
Which API operations have Cloud URLs?
Cloud URLs are available for Order Creation, Decoration Pricing, Hard Goods Pricing, Create Design, Products, Locations, and Ship Methods. Accepted Cloud Order Creation requests are queued and automatically forwarded when connectivity returns.
STANDARD API/Start here
Preflight Validation Checklist
Use this checklist before submitting an order. These checks reflect common
backend validation rules and the most frequent causes of rejected payloads.
Order header
Orders contains at least one order.
CustomerID, ContactID, and PoNumber are
present.
PoNumber is unique for the customer.
Customer access
The authenticated UserID matches the customer or parent customer.
ContactID exists, belongs to the customer, and is active.
The customer is not blocked by credit-limit validation.
Manifest
Each order has at least one manifest.
Each manifest has one or more line items.
DateToShip, when provided, is after the order date.
Line item
Each line item has an IntegrationProduct.
Each line item has at least one LineItemSize.
Every quantity is greater than zero.
Product
Product identifiers resolve to one product only.
Use ProductName with Mill or, if unique, VendorName. A supplier may carry several matching product records; in that case, use Mill or the exact ProductID.
Inventory parts use only one size row.
Design
Decorated items include Designs.
Existing designs include valid DesignID and colorway data.
New artwork includes FilePath and/or
CustomerDesignCode.
STANDARD API/Rules and support
Backend Processing Rules
Some submitted values are validated, normalized, or used to drive internal DMS
behavior after the request is received.
Area
Behavior
Customer impact
PoNumber
Trimmed before use. Values longer than the supported storage length are
shortened.
Keep PO values concise and unique. Avoid relying on characters near the end of
very long PO strings.
SecondaryPo
Trimmed and length-limited.
Use this for alternate references, not long notes.
EndUserPo
Trimmed and stored as a short end-user reference.
Use a compact value rather than a long freeform string.
OrderStatusNotificationUrl
Stored as the callback for order status events.
Use a stable, public HTTPS endpoint that can accept POST requests.
ShipmentNotificationUrl
Stored separately from the order status callback when supplied.
Use this when shipment-specific notification routing differs from general order
status routing.
Customer profile
Some behavior is customer-profile driven, including turn time, auto integration
approval, dynamic part creation, and customer-specific charges.
Your Dubow onboarding team can confirm which customer-profile rules apply to
your integration.
STANDARD API/Rules and support
Dates and Scheduling
Requested dates are treated as scheduling inputs. Dubow may adjust dates to
satisfy business-day and customer-profile rules.
Field
Behavior
Recommendation
Manifests[].DateToShip
Parsed as a date. Time-of-day is ignored. The final ship date may be moved to
the next business day and may be pushed out by the customer turn-time rule.
Submit the desired ship date, then use order status or webhooks to read the
final scheduled date.
Manifests[].DateDropDead
Parsed as a date. It cannot be earlier than the order date, ship date, or
scheduled date.
Use this only when there is a true deadline later than or equal to the requested
ship date.
Business days
Dates can be normalized to the next business day.
Avoid sending weekend or same-day ship dates unless explicitly approved.
Note
The default production turn-time rule may be overridden by customer profile. Confirm your
customer profile settings with Dubow during onboarding.
STANDARD API/Orders and status
POST ENDPOINTSubmit one or more orders
Order Creation
Use this endpoint to submit one or more orders to Dubow. Each order requires
authentication and must contain at least one manifest with one or more valid decorated line
items.
Use this Webhook/Endpoint to retrieve the current status of orders submitted to
Dubow. Status updates can also be received via webhook if configured.
Loading endpoint details…
Tip
If you include OrderStatusNotificationUrl in the Order Creation request, you
will receive automatic status updates via webhook and do not need to poll the status
endpoint.
Webhook Endpoint (Automatic)
Include OrderStatusNotificationUrl in your Order Creation request and we will
POST status updates to that URL.
One or more request objects used to look up order status.
RequestItems[].OrderID
integer
Conditional
Dubow Order Number. Required when CustomerPo is not provided.
RequestItems[].CustomerPo
string
Conditional
Customer Purchase Order Number. Required when OrderID is not provided.
Lookup requirement
Each RequestItems[] entry must contain either OrderID or CustomerPo. You do not need to provide both. Use one lookup value per request item for the clearest result.
Response Fields
Field
Type
Required
Description
ResponseSummary
object
Always
Includes IsSuccess, Errors, and
Authorization result for the call.
ResponseSummary.Authorization.TransactionID
string|null
No
Transaction identifier, may be null.
ResponseSummary.Authorization.UserID
integer
No
Authenticated user ID.
ResponseSummary.Authorization.Password
null
No
Redacted in responses.
ResponseSummary.Authorization.IsAuthenticated
boolean
Always
Authentication success flag.
Orders
array
When IsSuccess is true
Collection of order summaries.
Orders[].CustomerPo
string
No
Customer PO number.
Orders[].OrderID
integer
No
Internal Dubow order identifier.
Orders[].CustomerID
integer
No
Customer identifier.
Orders[].ReceivingStatus
string
No
Receiving state, for example No.
Orders[].ShippingStatus
string
No
Shipping state, for example No.
Orders[].IsInvoiced
boolean
No
Whether the order has been invoiced.
Orders[].IsCanceled
boolean
No
Whether the order has been canceled.
Orders[].ShippingCost
number
No
Order-level shipping cost returned as a JSON number, for example 0.
Orders[].HandlingCost
number
No
Order-level handling cost returned as a JSON number, for example 2.22.
Use this endpoint to retrieve invoicing and billing status for your submitted
orders. This is useful for reconciliation, accounts payable, and reporting workflows.
Use this GET endpoint to retrieve active product records and the exact values needed for order submission. Do not guess a product name, mill, size, or color. Call this endpoint first, then use the returned values in the order payload.
Loading endpoint details…
This is a read-only product lookup. Use returned product details to build an IntegrationProduct block in an order request.
How filters work
All query parameters are optional. Omit every parameter to return the full available product list. Supply one or more parameters to narrow the results. When combining parameters, all supplied filters are applied to the request.
The product style or part name to search for. Use the value returned in the response Name field when an exact match is required.
G500
productId
integer
No
The numeric product identifier returned in the response Id field.
5001
mill
string
No
The manufacturer or mill name. Use the spelling returned in the response Mill field.
Gildan
URL encoding
Query values containing spaces or special characters must be URL encoded. For example, Port Authority becomes Port%20Authority.
GET request examples
GETReturn the full product catalog
GET https://integration.dubowtextile.com/integration/orderintegrationservice.svc/json/products
GETFind a product by style or part name
GET https://integration.dubowtextile.com/integration/orderintegrationservice.svc/json/products?productName=G500
GETFind one product by numeric ID
GET https://integration.dubowtextile.com/integration/orderintegrationservice.svc/json/products?productId=5001
GETReturn products from one mill
GET https://integration.dubowtextile.com/integration/orderintegrationservice.svc/json/products?mill=Gildan
GETCombine product name and mill filters
GET https://integration.dubowtextile.com/integration/orderintegrationservice.svc/json/products?productName=K240&mill=Port%20Authority
Response fields
Field
Type
Meaning and reuse
Id
integer
Unique product identifier. May be sent back as productId in later lookup requests.
Name
string
Exact product style or part name. Use this value for product matching in integration payloads.
Description
string
Human-readable product description.
Mill
string
Exact manufacturer or mill name. Use this spelling when a mill is required to disambiguate the product.
ProductType
string
Product classification, such as T-Shirt.
IsActive
boolean
Indicates whether the product is currently active. Submit active products only.
RequiresMill
boolean
When true, the product style may require disambiguation. Prefer the returned Mill or exact ProductID; VendorName can also be used if it resolves to exactly one product.
Sizes
array<string>
Accepted size names for the product. Use these exact values in LineItemSizes[].SizeAsString.
Colors
array<string>
Available product colors. Use the returned spelling when supplying a product color.
Creates one or more standalone designs before they are used on an order. Each design identifies the artwork, decoration method, finished dimensions, location, and one or more colorways.
Loading endpoint details…
Use this endpoint to create a new design. To reference an existing design while placing an order, use the Designs[] order fields instead.
Direct HTTPS URL to the source artwork file. The URL must be accessible to Dubow without an interactive login.
Designs[].Location
string
Yes
Garment or imprint location. Use a value returned by the Locations endpoint.
Designs[].Colorways
array
Yes
At least one colorway describing garment color and colorway-specific artwork instructions.
Designs[].ContactID
integer
Account-dependent
Dubow contact receiving or owning the design.
Designs[].ProgramID
integer
No
Program to associate with the design when applicable.
Designs[].AdditionalNotes
string
No
Production or art instructions.
Designs[].IsHat
boolean
No
Indicates that the design is intended for headwear.
Designs[].ProportionalBy
string
No
Dimension used to preserve proportions, for example Width.
Designs[].ChargePONumber
string
No
PO reference used for applicable design charges.
Designs[].AdditionalServices
array of strings
No
Requested design services, for example Digitizing.
Available Decoration Method Names
Use one of these method names in Designs[].DesignTypeName.
Applique
Digital Print
Direct to Film
Dye Sublimation
Embroidery
Screen Print
HG Flat
HG Cylindrical
HG Dye Sublimation
Heat Transfer
Laser Etch
Pad Print
Ultra Print
Magnet
Pinback Button
Sticker
Poster
Colorway fields
Field
Type
Required
Description
Colorways[].GarmentColor
string
Yes
Garment color this colorway is intended for.
Colorways[].Notes
string
No
Colorway-specific instructions.
Colorways[].CustomerColorwayCode
string
No
Customer's identifier for the colorway.
Colorways[].ColorwayFileUrl
string URL
No
Direct URL to a colorway-specific preview or artwork file.
Colorways[].Breaks
array
Conditional
Thread, ink, or production break details for this colorway.
Using production breaks
When your design requires thread, ink, or production breaks, contact Dubow for the accepted values to include in Colorways[].Breaks. The example below uses an empty array.
Call-level success, errors, and authorization result. See ResponseSummary.
Results
array
Successful result
One result object for each design processed by the request.
Results[].IsCreated
boolean
Per result
Indicates whether the design was created.
Results[].DesignID
integer
Per result
Dubow design identifier assigned to the created design. Save this value for later order submissions.
Results[].OrderID
integer or null
Per result
Order identifier when the creation workflow is associated with an order. The supplied standalone design example returns null.
Results[].PoNumber
string or null
Per result
PO reference returned for the design result. In the supplied example it reflects ChargePONumber.
Results[].Colorways
array
Per result
Colorways created for the design.
Results[].Colorways[].Number
integer
Per colorway
Dubow colorway number assigned to the created colorway.
Results[].Colorways[].Name
string
Per colorway
Returned colorway name. The supplied example uses the garment color.
Results[].MessagesOnDesign
value or null
Per result
Design-level messages when returned. The supplied successful example returns null.
Save the returned IDs
After creation, retain DesignID and the returned colorway Number values. They identify the newly created design and colorways for subsequent integration workflows.
Use the pricing endpoints to retrieve decoration price grids or hard goods pricing. Choose the endpoint based on whether the request is for a decoration method or a hard goods part.
Fields that do not apply to the selected decoration method may be omitted from PricingRequest or included with a value of null. The examples below omit unused fields to keep requests concise.
Accepted PricingType values
Value
When to use
ProgramID
Program
Retrieves pricing assigned to a specific Dubow program.
Required. Supply the numeric program ID provided by Dubow.
Integrated
Retrieves integration-specific pricing available to the authenticated customer.
Omit or set to null unless Dubow instructs otherwise.
Default
Retrieves the default pricing grid.
Omit or set to null.
DecorationMethod and measurement rules
Use the exact supported method name. See Available Decoration Method Names for the complete business-facing list. The pricing specification explicitly confirms the API values shown below.
DecorationMethod value
Required pricing fields
Fields to omit or set to null
ScreenPrint
Quantity, Colors
StitchCount, Height, Width
PadPrint
Quantity, Colors
StitchCount, Height, Width
Applique
Quantity, StitchCount
Colors, Height, Width
Embroidery
Quantity, StitchCount
Colors, Height, Width
Other enabled methods
Quantity, Height, Width
Colors, StitchCount
Available Decoration Method Names
Use the exact documented name in PricingRequest.DecorationMethod, design creation, or order payload fields where a decoration method is required.
VALUESSupported decoration method names
Applique
Digital Print
Direct to Film
Dye Sublimation
Embroidery
Screen Print
HG Flat
HG Cylindrical
HG Dye Sublimation
Heat Transfer
Laser Etch
Pad Print
Ultra Print
Magnet
Pinback Button
Sticker
Poster
Common names
Direct to Film may be referred to as DTFx, and Ultra Print may be referred to as UVTx. Submit the formal decoration method name shown above unless Dubow has approved another account-specific value.
Exact API spelling
The available-method list uses readable names such as Digital Print and Direct to Film. Confirm the exact API value with Dubow before sending a method that is not one of the four explicitly defined above.
The pricing response contains the shared ResponseSummary plus a PriceGrid object. Each object in PriceGrid.Prices[] is a returned pricing tier.
Field
Type
Returned
Meaning
ResponseSummary
object
Always
Call-level success, errors, and authorization result. See ResponseSummary.
PriceGrid
object
Successful result
The resolved pricing grid and its pricing tiers.
PriceGrid.PricingType
string
Successful result
Pricing type resolved for the result, such as Program, Integrated, or Default.
PriceGrid.ProgramID
integer or null
Successful result
Program identifier associated with the returned grid when applicable.
PriceGrid.DecorationMethod
string
Successful result
Decoration method represented by the returned grid.
PriceGrid.PriceGridName
string
Successful result
Readable name of the pricing grid that was selected.
PriceGrid.Currency
string
Successful result
Currency used by the returned prices. The supplied example returns USD.
PriceGrid.PricingModel
string
Successful result
Pricing model for the grid. The supplied example returns Matrix.
PriceGrid.Prices
array
Successful result
Pricing tiers returned for the resolved grid.
PriceGrid.Prices[].Colors
integer
Method-dependent
Color count represented by this tier for color-based methods such as Screen Print or Pad Print.
PriceGrid.Prices[].MinimumQuantity
integer
Tier field
Lowest quantity included in the returned tier.
PriceGrid.Prices[].MaximumQuantity
integer
Tier field
Highest quantity included in the returned tier.
PriceGrid.Prices[].UnitPrice
decimal
Tier field
Per-unit decoration price for that returned tier.
How to use the tiers
Match the order quantity to the tier whose MinimumQuantity and MaximumQuantity contain that quantity. UnitPrice is the price returned for that tier. Method-specific measurement fields can differ by decoration method.
Use the values below rather than the complete internal PR- PartName or a color-specific suffix. Group values such as Sticker, Mug, and Poster return the matching products in that family.
Request fields
Field
Type
Required
Description
Authorization
object
Yes
Standard Dubow authorization block.
PartName
string
Yes
Use one supported search value from the table below.
Supported hard goods search values
PartName search value
Description
Mug
Ceramic and stainless mugs in available sizes and colors.
Button
Pinback buttons in available round and square sizes.
Poster
Printed posters in available dimensions.
Sticker
Printed stickers in available sizes.
CanCooler
Classic and skinny can coolers in available finishes.
Webhooks allow you to receive real-time updates about your orders without
polling the API. Simply include a webhook URL in your order submission to be notified when
key events occur.
Include callback URLs in the order request when you want Dubow to push updates instead of
relying only on polling.
Include OrderStatusNotificationUrlorShipmentNotificationUrl in your IntegrationOrder
These fields function identically. Dubow will send the same JSON payload to either
Must be a valid HTTPS URL that can accept JSON POST payloads
Best Practices
Return HTTP 200 OK to acknowledge receipt
Log payloads and timestamps for reconciliation
Implement retry logic in case of delivery failure or timeout
STANDARD API/Order JSON structure
Manifests
A manifest groups one or more line items being shipped to the same address with
a shared shipping method. Each order must contain at least one manifest.
An order contains manifests. Each manifest contains shipping details and line items. Each line item contains product data, quantities, artwork designs, and optional services. Follow this structure when building the Orders[] JSON.
Not all fields shown are mandatory for every request. A ReturnAddress, when used, is an order-level field, not part of ShipToAddress. Check each reference page for conditional fields and valid identifiers.
Order JSON example
This is a syntactically valid example request with placeholder account, product, and design identifiers. Replace those values before testing.
VendorName is a supplier filter, not the manufacturer's Mill and not a unique identifier. For example, ProductName2000 with VendorNameS&S Activewear can return several product records. In that case, provide the correct Mill or use the exact ProductID. The sample above is illustrative and must resolve to one product to succeed.
This object identifies which product is being decorated and how it is sourced.
Field
Type
Required
Description
ProductName
string
Yes*
Product identifier (e.g. 2000)
Mill
string
Conditional
Garment manufacturer or brand, for example Gildan. Use when the ProductName is ambiguous, including when a supplier lookup using VendorName produces multiple matches.
VendorName
string
No
Supplier name, for example Sanmar or S&S Activewear. Can be used with ProductName as an alternative to Mill when the combination identifies one product. Multiple products may share the same name and vendor, so use Mill or ProductID if the lookup remains ambiguous.
Description
string
Yes
Text description of the product
ProcurementType
string
Yes
Contract, or Custom
CustomerProductName
string
Conditional
Used only if customer is enabled for part creation. Unlike
ProductName, which errors if missing, this field allows dynamic
part creation.
VendorProductName
string
No
Vendor style number
ProductTypeName
string
No
Category name (e.g. Apparel, Tote)
Color
string
No
Color description
ProductID
int
No
Internal Dubow ID
Notes
string
No
Internal product notes
Urls
array
No
Array of preview or mockup images
Product Lookup Priority and Ambiguity Rules
Dubow resolves the product to a single internal part before the order can be created. Use the
most specific identifier available and avoid sending conflicting identifiers.
Recommended order
Field pattern
Best use
1
ProductID
Use when Dubow has provided the internal product ID.
2
ProductName + Mill
Use for catalog products where the same style number may exist under multiple
mills.
3
ProductName + VendorName
Use when the supplier, such as Sanmar or S&S Activewear, is known but the Mill is not. This succeeds only when the combination resolves to one product; otherwise add the correct Mill or use ProductID.
4
CustomerProductName
Use when Dubow has mapped your SKU to a Dubow product or when dynamic part
creation is enabled.
5
VendorProductName + Mill
Use when the vendor style is the known lookup value.
Avoid conflicting identifiers
If multiple product identifiers are provided and they resolve to different internal
products, the request can fail because the product is ambiguous.
Dynamic Part Creation
Some customers are configured for automatic part creation through integration. This is
customer-profile controlled and is not enabled for every customer.
Requirement
Description
CustomerProductName
Required. Used to create or look up the customer-specific product.
Description
Required. Used as the new product description.
Color
Required. Used as the product color.
Customer profile setting
Dynamic part creation must be enabled by Dubow for the customer.
Created part naming
When dynamic creation is enabled, Dubow creates the internal product using a
DYN- prefix followed by the submitted CustomerProductName.
ProcurementType Values
Value
Description
Contract
You supply the garments and Dubow decorates and ships per your manifests.
Custom
Dubow procures product from your specified vendor; include detailed
Description in IntegrationProduct.
LineItemSizes
JSONContract apparel line item
with multiple sizes
This section describes Designs[] inside an order creation payload. To create a reusable design independently, use the Create Design endpoint.
Screen print minimum
Screen print designs require a minimum quantity of 24 units per colorway. Orders below
this minimum may be rejected during validation.
Requirements
Existing design: DesignTypeName, DesignID, and
IntegrationColorway are required. Design via URL: DesignTypeName, FilePath
and/or CustomerDesignCode, and IntegrationColorway are
required. Keep examples exactly as shown.
Internal design identifier when referencing an existing design.
FilePath
string (URL or path)
Yes (Design via URL)
Location of the artwork file when submitting via URL.
CustomerDesignCode
string
Yes (Design via URL)
Your reference code for the artwork when submitting via URL.
IntegrationColorway
object
Yes
Placement and preview information for the decoration.
Urls
array<UrlRef>
No
Optional previews or mockups that accompany the design.
Customizations
array<Customization>
No
Name and number personalizations for this placement. See Customizations.
Available Decoration Method Names
Use one of these method names in DesignTypeName.
Applique
Digital Print
Direct to Film
Dye Sublimation
Embroidery
Screen Print
HG Flat
HG Cylindrical
HG Dye Sublimation
Heat Transfer
Laser Etch
Pad Print
Ultra Print
Magnet
Pinback Button
Sticker
Poster
Association/Dual Designs:
DesignID may reference an associated design (a design that contains multiple
child design numbers).
When you send a DesignID for an associated design, you must provide
GarmentLocationName as a single string with one
location per child design, in the same order, separated by a forward slash “/”. Tip: Find the correct associated DesignID and ColorwayID in DOTS (search by title, code, or keyword) and
paste them into your
payload to avoid mismatches.
This object defines where and how the design will be applied. It is always required, even
when submitting art via URL.
Field
Type
Required
Description
ColorwayID
integer
Yes/No
Only Required when using Designs[].DesignID.
CustomerColorwayCode
integer
Yes/No
Only Required when using Designs[].CustomerDesignCode.
Colors
array<Colors>
Conditional
Thread or ink colors for this placement. Required for Embroidery and
Screen Print when you need to specify thread/ink colors. Omit for
methods that do not use thread/ink color assignments.
GarmentLocationName
string
Yes
Placement such as Left Chest or FULL Back.
Urls
array<UrlRef>
No
Preview images or references shown in examples.
Colors (ThreadBreaks/Ink Colors)
Use this array inside IntegrationColorway to define specific thread or ink
colors.
Field
Type
Required
Description
Color
string
Yes
Thread or ink color name, for example Super White.
Ordinal
integer
Yes
Position or needle index for the color. Start at 1 and keep unique
within the placement.
Map
string
Yes
Short description of what is in specified ordinal. (eg "Icon", "Text", "Trim")
Customizations (Personalizations)
Use this array inside Designs to define individual name/number customizations.
Important Note
Personalization will be used on the full quantity of the current integration
product object.
For example, if the line item quantity is 5, and there is 1 customization defined, that
same customization will be applied to all 5 items.
To have different customizations for each item, you must create separate integration
products for each unique customization.
Shipping details are defined within the Manifests array of each
order. Each order must include at least one manifest, and each manifest must include a
complete ShipToAddress and at least one line item.
One or more decorated items included in the shipment.
IsResidential
boolean
No
Residential address flag.
ThirdPartyAccountNumber
string
No
Account number for third-party shipping billing.
PackingSlipUrl
string (URL)
No
Link to a PDF packing slip to include in the carton.
Notes
string
No
Manifest-level instructions or notes.
ShipToAddress Fields
This is a nested object required inside each manifest. The more complete the address, the
more accurate the label and delivery rate.
Required Fields
Field
Type
Required
Description
Address1
string
Yes
Recipient or attention line (for example the person or department).
Address3
string
Yes
Street address line as used in examples.
City
string
Yes
City.
State
string
Yes
State or province 2-letter code. **Only Required when Country is "US"**
Zip
string
Yes
Postal code.
Country
string
Yes
2-letter country code, for example US.
Address2
string
No
Optional Additional Recipient or attention line (for example the person or
department)
Address4
string
No
Optional delivery information such as apartment, suite, unit, floor, or building
name. Also used for “Care Of” or company names if Address1 is a personal name.
Address5
string
No
Optional Extra locality details that don’t fit in City/State/ZIP, such as
districts, suburbs, villages, or neighborhoods (often needed for non-U.S.
addresses)
PhoneNumber
string
No
Contact number for delivery
EmailAddress
string
No
Contact email
Ship Methods
Select the carrier/service for each manifest using ShipMethodAbbreviation. Use
the Ship Methods JSON endpoint to retrieve the exact abbreviations supported.
Field
Type
Required
Description
ShipMethodAbbreviation
string
Yes
Carrier/service code from the Shipping Methods feed. Use the exact abbreviation
shown there.
You can request optional add-on services at the line item level using the
Services array. These services support finishing, packaging, and branding
enhancements.
If your request contains invalid or incomplete data, Dubow’s API will return a
structured response containing helpful error messages to aid troubleshooting.
Response Structure
All error responses follow this format:
JSONError response format
{
"ResponseSummary": {
"IsSuccess": false,
"Errors": [
{
"Message": "Description of the problem."
}
]
}
}
Common Error Messages and How to Fix Them
Search for an error message or select a category to find the cause and recommended fix. Decoration restrictions identify product and imprint combinations that cannot be used.
Showing 66 of 66 errors
No errors match your search. Try another term or category.
Auth
Unauthorized. Please check UserID and Password.
Likely cause
The Authorization block is missing, incorrect, or using credentials
for the wrong environment.
How to fix
Confirm Authorization.UserID, Authorization.Password,
and whether you are calling sandbox or production.
Auth
Invalid Authorization UserId
Likely cause
The request user ID is missing, zero, or not recognized.
How to fix
Use the assigned Dubow API UserID. If using a child customer, the
authenticated user must be allowed to submit for that customer.
Order
Orders list is Empty
Likely cause
The request did not include any orders in Orders[].
How to fix
Send at least one order object inside the Orders array.
Order
A PoNumber (Purchase Order Number) was not given.
Likely cause
The order is missing PoNumber or it is blank.
How to fix
Send a non-empty, unique PoNumber for every order.
Order
This PO already exists in our system. Duplicate?
Likely cause
The submitted PoNumber already exists for that customer.
How to fix
Use a unique PoNumber. For resubmits, use a revision value such as
PO12345-REV1.
Order
Duplicate order. This PONumber already exists.
Likely cause
Same as duplicate PO. The customer PO has already been accepted or created.
How to fix
Do not resend the same PO unless directed. Use a new PO value when submitting a
replacement order.
Order
Duplicate PONumber for CustomerID
Likely cause
Duplicate PO for the submitted CustomerID.
How to fix
Use a unique PoNumber for the customer.
Order
Is not a valid CustomerID.
Likely cause
The submitted CustomerID does not exist.
How to fix
Confirm the customer/company ID with Dubow.
Order
is not a valid child customer
Likely cause
The authenticated user is not allowed to submit orders for the requested child
customer.
How to fix
Use the correct child customer or request that Dubow assign access to the
authenticated parent customer.
Order
Customer is in excess of their Credit Limit.
Likely cause
The account is blocked by a credit limit rule.
How to fix
Contact Dubow support or accounting before resubmitting.
Order
is not a valid ContactID.
Likely cause
The submitted ContactID does not exist.
How to fix
Confirm the contact ID with Dubow.
Order
The Contact's owning Customer is not the specified Customer.
Likely cause
The contact exists but belongs to a different customer.
How to fix
Use a ContactID that belongs to the submitted
CustomerID.
Order
Contact is not active.
Likely cause
The contact exists but is inactive.
How to fix
Use an active contact assigned to the same customer.
Order
The Order didn't contain any Manifests.
Likely cause
The order did not include Manifests[].
How to fix
Add at least one manifest with shipping and line item details.
Payload
Unable to parse payload
Likely cause
The request body is not valid JSON or the content type is wrong.
How to fix
Validate the JSON and send Content-Type: application/json.
Payload
One or more required fields are missing or invalid
Likely cause
A required field is missing, misspelled, or using the wrong type.
How to fix
Compare your payload with the required examples and field reference.
Shipping
An IntegrationManifest cannot be scheduled to ship on a date earlier than or equal to the day it is placed
Likely cause
DateToShip is today or in the past.
How to fix
Use a future valid ship date and account for Dubow turn time rules.
Shipping
An IntegrationManifest cannot have a deadline date earlier or equal to the day it is placed.
Likely cause
DateDropDead is today or in the past.
How to fix
Use a future deadline date.
Shipping
Each IntegrationManifest must define at least one LineItems.
Provide the required shipping address fields listed in the shipping section.
Shipping
Address must have at least one of Address1,2,3
Likely cause
No address line was supplied.
How to fix
Provide a complete ShipToAddress. Keep using the stricter address
requirements documented above.
Shipping
FedEx ship methods can only be used with a provided 3rd Party Account#.
Likely cause
The selected FedEx method requires a third-party shipping account.
How to fix
Provide the appropriate third-party account number in the manifest, or select another available shipping method.
Shipping
Ship method '{abbr}' does not support a 3rd Party Account#. Remove the 3rd Party Account# or choose a ship method that supports it.
Likely cause
The selected shipping method does not allow third-party billing.
How to fix
Remove the third-party account number, or choose a ship method that supports third-party billing.
Product
A ProductName was given without a Mill and no match or multiple was found
Likely cause
ProductName is ambiguous or not found.
How to fix
Include Mill, use ProductID, or confirm product
mapping from Lookup Lists.
Product
A ProductName was given without a Mill: Multiple products were found with name
Likely cause
ProductName and the supplied VendorName matched more than one internal ProductID. A valid vendor name does not guarantee a unique match.
How to fix
Verify the intended product and resubmit with its Mill or exact ProductID. For example, a lookup for 2000 under S&S Activewear can match multiple records.
Product
A ProductName was given with a Mill and no match or multiple was found
Likely cause
The product and mill combination did not resolve.
How to fix
Verify the product style and mill combination in Lookup
Lists.
Product
A VendorProductName was given with a Mill and no match or multiple was found
Likely cause
The vendor product lookup failed.
How to fix
Verify VendorProductName and Mill, or use another
supported product lookup path.
Product
An Invalid ProductID was specified
Likely cause
The submitted ProductID does not exist.
How to fix
Use a valid Dubow product ID from the product lookup list.
Product
Each IntegrationProduct must unambiguously specify a Product
Likely cause
Multiple product identifiers resolve to different products.
How to fix
Use one clear lookup method, or make sure all product fields resolve to the same
part.
Product
Cannot lookup inventory. SKU does not exist or multiple in the system.
Likely cause
The inventory SKU is missing, inactive, or ambiguous.
How to fix
Confirm the SKU with Dubow or use a more specific product identifier.
Product
Inventory metadata did not sync
Likely cause
OrderDesk did not find a matching inventory item from the incoming store SKU, so the saved metadata fields were not copied to the order item.
How to fix
Make the store SKU match the OrderDesk inventory item Code/SKU, then sync item details with inventory before resubmitting.
Product
print_sku is missing or incorrect
Likely cause
The item has a store SKU but does not have the Dubow product SKU metadata needed for production.
How to fix
Add print_sku to the inventory item metadata and confirm mill or print_mill when required.
Product
Not possible to dynamically create an integration product
Likely cause
The customer is not enabled for dynamic part creation, or required fields are
missing.
How to fix
Confirm setup with Dubow and include CustomerProductName,
Description, and Color.
Product
[PartNumber] is an inactive part.
Likely cause
The product exists but is inactive.
How to fix
Remove the item or contact Dubow to verify availability.
Product
An invalid VendorID was specified: '{vendorId}'
Likely cause
The vendor identifier is not recognized by Dubow.
How to fix
Confirm the correct VendorID, or identify the supplier with VendorName and resolve the product to a single match.
Product
No vendor was found matching VendorName '{name}'
Likely cause
The supplied VendorName does not match a supplier in Dubow.
How to fix
Check the vendor spelling and use a recognized name, such as Sanmar or S&S Activewear.
Product
Multiple products were found with name '{name}' supplied by {vendor} (ProductIDs: {ids}). Provide a Mill or ProductID to disambiguate
Likely cause
The product name and supplier match more than one Dubow product.
How to fix
Specify the correct Mill or exact ProductID to select a single product.
Size
Each LineItem must have at least one LineItemSize to define size and quantity.
Likely cause
The line item is missing LineItemSizes[].
How to fix
Add at least one size row with quantity.
Size
LineItem for Dubow Owned Inventory Part should not contain more than 1 LineItemSize.
Likely cause
A Dubow-owned inventory line item has multiple size rows.
How to fix
Send one size row only or split inventory products into separate line items.
Size
Each LineItemSize must have a quantity greater than 0.
Likely cause
Quantity is zero, negative, or missing.
How to fix
Set every LineItemSizes[].Quantity value to a positive integer.
Size
Quantity must be greater than 0
Likely cause
Quantity is zero, negative, or missing.
How to fix
Use positive integer quantities.
Size
Each LineItemSize must specify a SizeIndex either in string or integer enumeration.
Likely cause
The line item size cannot be determined.
How to fix
Send a valid SizeAsString or SizeIndex.
Size
An unambiguous size cannot be determined for all LineItems.
Likely cause
The supplied size text cannot be mapped.
How to fix
Use a supported size format such as XL, 2XLT, or
Medium.
Size
SizeAsString value is not recognized
Likely cause
The size value is not recognized.
How to fix
Use a supported size format from the documentation.
Design
No IntegrationDesigns included with LineItem X but NoDecoration does not equal true
Likely cause
A decorated item is missing Designs[].
How to fix
Add Designs[], set NoDecoration: true, or use the
inventory workflow.
Design
Missing Design Reference
Likely cause
The design did not include DesignID,
CustomerDesignCode, DesignCode, or
FilePath.
How to fix
Provide a valid existing design reference or send a design URL workflow with
DesignTypeName.
Design
Could not use DesignID, DesignCode or CustomerDesignCode...
Likely cause
No existing design could be resolved and no valid design type was provided for
new art.
How to fix
Use a valid design reference or include DesignTypeName for new art.
Design
DesignID does not exist.
Likely cause
The submitted design ID is not valid.
How to fix
Confirm the design in DOTS or use a valid CustomerDesignCode or
design URL workflow.
Design
DesignID not found or not valid for account
Likely cause
The design is missing or not assigned to the customer.
How to fix
Use a valid, customer-authorized DesignID.
Design
Customer does not have rights to DesignID
Likely cause
The design exists but is not available to the submitted customer.
How to fix
Use a customer-owned design or request Dubow to assign rights.
Design
Cannot resolve DesignCode
Likely cause
The submitted design code did not resolve to a design.
How to fix
Use a valid DesignID, DesignCode,
CustomerDesignCode, or design URL workflow.
Design
DesignTypeName is required
Likely cause
New art or design resolution needs a decoration type.
How to fix
Set DesignTypeName in the design block, for example
Embroidery.
Design
There are multiple colorways for this design, but no colorway was provided. Please provide a colorway.
Likely cause
The design has multiple colorways and none was selected.
How to fix
Send IntegrationColorway.ColorwayID with the existing
DesignID.
Design
ColorwayID not found or not associated with DesignID
Likely cause
The colorway is invalid or does not belong to the design.
How to fix
Verify the ColorwayID belongs to the specified
DesignID.
Design
Incorrect number of thread breaks (Ordinal) called for Design ####. - X of Y Colors Received
Likely cause
The submitted color ordinals do not match the design's thread breaks.
How to fix
Update IntegrationColorway.Colors[] ordinals to match the design.
Design
Design #### is an associated design and requires additional locations in "GarmentLocationName" split by a "/" for each location
Likely cause
An associated design requires multiple locations in order.
How to fix
Send slash-separated locations such as Full Front/Full Back.
Design
FilePath is not a valid URL
Likely cause
The art URL is malformed or inaccessible.
How to fix
Use a properly formatted, publicly accessible https:// link.
Design
Design FilePath and DesignID cannot be used together
Likely cause
The payload mixes an existing design with new-art submission.
How to fix
Choose either existing design fields or design URL fields, not both.
Design
CustomerDesignCode already used on another design
Likely cause
The customer design code is not unique.
How to fix
Use a unique CustomerDesignCode or reuse the existing design
reference if intended.
Design
Less than 24qty used per colorway for screen print.
Likely cause
Screen print line quantity is below the minimum.
How to fix
Increase the quantity to at least 24 units per colorway or use another approved
decoration method.
Services
A service code was provided that is not supported
Likely cause
The service name/code does not map to a valid service part.
TEST URL! This error will only appear on test requests.
Likely cause
The test endpoint is returning its test-mode confirmation message.
How to fix
No production action is needed. Use this only to verify test behavior.
Payload
TrackingNumber cannot be blank when OrderStatus is Shipped
Likely cause
A shipped status update is missing tracking information.
How to fix
Provide a valid TrackingNumber when sending or consuming shipped
updates.
Decoration
Part {partName} is not available for the {designType} decoration method.
Likely cause
The specified product is restricted from the selected decoration method.
How to fix
Choose a permitted decoration method for this product or select a different product. Contact API Support if the restriction needs review.
Decoration
Part {partName} is not available for the {location} imprint location.
Likely cause
The specified product is restricted from the selected imprint location.
How to fix
Choose another imprint location permitted for this product or select a different product. Contact API Support if needed.
HTTP Status Codes
Status
Meaning
When it happens
200
OK
Successful request with IsSuccess true.
400
Bad Request
Malformed JSON or missing required fields.
401
Unauthorized
Invalid Authorization credentials.
404
Not Found
Endpoint or resource not found.
429
Too Many Requests
Rate limit exceeded.
500
Server Error
An unexpected error occurred.
Best Practices
Always inspect ResponseSummary.IsSuccess before processing
Log errors with ResponseSummary.Errors[].Message
Validate your payload against field requirements before submission
Use test mode with realistic payloads before sending live orders
JSONSample Error
Response
{
"ResponseSummary": {
"IsSuccess": false,
"Errors": [
{
"Message": "A ProductName was given without a Mill and no match or multiple was found: 'PR-10000-Black-M'"
},
{
"Message": "Each IntegrationProduct must unambiguously specify a Product: PR-10000-Black-M."
},
{
"Message": "No IntegrationDesigns included with Lineitem PR-10000-Black-M but NoDecoration does not equal true."
},
{
"Message": "TEST URL! This error will only appear on test requests."
}
]
}
}
STANDARD API/Start here
Sandbox & Test Mode
Use unique PO values for every test. Keep customer, contact, product, and design values
aligned with the test account setup.
Dubow’s integration environment supports full-featured testing without
affecting live orders or production. You can validate payloads, test error handling, and
preview responses using all the exact same information in this documentation.
Test orders are accepted and validated but are never routed to the production
environment
Some responses will contain the message:
TEST URL! This error will only appear on test requests.
You can simulate real orders with full data, including designs and manifests
What You Can Test
Validation errors for missing fields
Design handling (FilePath and DesignID logic)
Webhook callbacks (with your own test URL)
OrderStatus API behavior and responses
Best Practices
Use unique PoNumbers (prefixed with TEST- or similar) to avoid conflicts
Do not mix test orders with live artwork or production POs as they will not be processed
Use OrderStatusNotificationUrl pointing to a test endpoint to verify
webhook behavior
STANDARD API / Examples and tools
JSON syntax checker
Paste a request or response to verify JSON syntax and check its top-level structure. Validation runs entirely in this browser. No API request is sent. This does not validate product IDs, customer permissions, inventory, or business rules.
Paste a JSON document to see syntax and basic request-shape results.
A JSON syntax check cannot confirm whether the API will accept a request. For product matching and validation rules, see the Preflight checklist and Product lookup rules.
STANDARD API/Examples and reference
API Field Finder
Field reference
Find an API field
Search the fields documented throughout the API, including requests, responses, pricing, product lookups, and OrderDesk metadata. Choose a result to jump to its definition.
369indexed fields
Loading field reference… Example-only entries are labeled and may require confirmation.
Field name / path
API area
Used in
Requirement
Details
No matching fieldsTry a different name, area, or usage filter.
This index includes every named field in the supplied reference tables, plus fields visible in JSON examples. Example-only fields are identified separately and do not establish backend support. Some requirements vary by request type or customer configuration.
This glossary consolidates all request and response objects. Use the bracket notation to
understand where arrays occur, for example Orders[].Manifests[].LineItems[].
Authorization (request)
Path: Authorization (top-level in request bodies)
Field
Type
Required
Description
UserID
integer
Yes
API user identifier issued by Dubow.
Password
string
Yes
API user password for the given UserID.
IntegrationOrder (creation)
Path: Orders[]
Field
Type
Required
Description
CustomerID
integer
Yes
Company identifier in DMS. Provided by Dubow.
ContactID
integer
Yes
Customer/contact identifier in DMS. Provided by Dubow.
PoNumber
string
Yes
Customer purchase order number.
Manifests
array<Manifest>
Yes
One or more shipping manifests, each with at least one LineItem.
ReturnAddress
object
Conditional
Include to override the default return address for the order. See ReturnAddress.
OrderStatusNotificationUrl
string (URL)
No
Webhook endpoint for status updates. If present, payload mirrors Order Status
response.
ShipmentNotificationUrl
string
No
HTTPS URL for automatic shipment notifications. See Webhooks.
SecondaryPo
string
No
Secondary purchase order reference.
EndUserPo
string
No
End-customer PO reference.
Platform
string
No
Source platform identifier, if applicable.
CustomerStore
string
No
Customer program or store code, if applicable.
Notes
string
No
Order-level notes for production or customer service.
Manifest
Path: Orders[].Manifests[]
Field
Type
Required
Description
ShipMethodAbbreviation
string
Yes
Carrier/service code from the Shipping Methods feed. See Ship Methods.
Used with all ProcurementType's; SKU or style, for example
2000.
Mill
string
Conditional
Manufacturer or brand used to disambiguate ProductName, including when a vendor filter yields multiple products.
VendorName
string
No
Optional supplier name, for example Sanmar or S&S Activewear. Can be used with ProductName instead of Mill when it identifies exactly one product. If more than one record matches, supply Mill or the specific ProductID.
CustomerProductName
string
Conditional
Used for Contract and Custom procurement; used only if
customer is enabled for part creation. If value is not found, system creates a
new dynamic part as DYN-[value], e.g. PC099 →
DYN-PC099. Unlike ProductName, which errors if
missing, this field allows dynamic part creation.
State or province code. **Only Required when Country is "US"**
Zip
string
Yes
Postal code.
Country
string
Yes
2-letter country code, for example US.
Address2
string
No
Optional Additional Recipient or attention line (for example the person or
department).
Address4
string
No
Optional delivery information such as apartment, suite, unit, floor, or building
name. Also used for “Care Of” or company names if Address1 is a personal name.
Address5
string
No
Optional Extra locality details that don’t fit in City/State/ZIP, such as
districts, suburbs, villages, or neighborhoods (often needed for non-U.S.
addresses).
PhoneNumber
string
No
Contact number for delivery.
EmailAddress
string
No
Contact email for delivery updates.
ReturnAddress
Path: Orders[].ReturnAddress
Field
Type
Required
Description
Address1
string
Yes
Recipient or Attention line.
Address3
string
Yes
Street address line.
City
string
Yes
City.
State
string
Yes
State or province code. **Only Required when Country is "US"**
Zip
string
Yes
Postal code.
Country
string
Yes
Country name or code.
Address2
string
No
Optional Additional delivery information such as apartment, suite, unit, floor,
or building name. Also used for “Care Of” or company names if Address1 is a
personal name.
Address4
string
No
Optional Extra locality details that don’t fit in City/State/ZIP, such as
districts, suburbs, villages, or neighborhoods (often needed for non-U.S.
addresses)
Address5
string
No
Optional field for secondary administrative areas, international province codes,
or other special delivery notes that must be part of the mailing label
PhoneNumber
string
No
Contact phone.
EmailAddress
string
No
Contact email.
RequestItems (Order Status)
Path: RequestItems[] in Order Status request
Field
Type
Required
Description
OrderID
integer
Conditional
Dubow Order Number. Required when CustomerPo is not provided.
CustomerPo
string
Conditional
Customer Purchase Order Number. Required when OrderID is not provided.
Required pointer
At least one lookup field is required per RequestItems entry: OrderID or CustomerPo. Both are not required.
RequestItems (Invoice Status)
Path: RequestItems[] in Invoice Status request
Field
Type
Required
Description
CustomerPo
string
Yes
PO number to query.
ResponseSummary
Path: ResponseSummary in responses
Field
Type
Required
Description
IsSuccess
boolean
Yes
True when the request succeeded.
Authorization
object
Yes
Authentication result details. See below.
Errors
array<Error>
Varies
Contains error entries when a request fails and may be an empty array ([]) when successful. Each entry has a Message field.
ResponseSummary.Authorization
Field
Type
Required
Description
IsAuthenticated
boolean
Yes
True when the provided credentials are valid.
TransactionID
string|null
No
Transaction identifier for troubleshooting; may be null.
UserID
integer
No
Authenticated user id.
Password
null
No
Redacted in responses.
Error
Path: ResponseSummary.Errors[]
Field
Type
Required
Description
Message
string
Yes (per error entry)
Human-readable explanation of the error. The Errors array can be empty when a request succeeds.
Order (status response)
Path: Orders[] in Order Status response
Field
Type
Required
Description
CustomerPo
string
No
PO number returned for reference.
OrderID
integer
No
Internal Dubow order identifier.
CustomerID
integer
No
Customer identifier.
ReceivingStatus
string
No
Receiving state, for example No.
ShippingStatus
string
No
Shipping state, for example No.
IsInvoiced
boolean
No
Whether the order has been invoiced.
IsCanceled
boolean
No
Whether the order has been canceled.
ShippingCost
number
No
Order-level shipping cost returned as a JSON number, for example 0.
HandlingCost
number
No
Order-level handling cost returned as a JSON number, for example 2.22.
OrderStatus
string
No
Current stage of the order, for example Entered. See OrderStatus
value list in the Order Status section.
UniqueTrackingNumbers
array<UniqueTrackingNumber>
No
Distinct tracking objects for the order. See below.
Shipment timestamp, for example 2025-08-04T12:51:00.
ShipMethodName
string
No
Readable carrier service name.
ShipperReference
string
No
Reference from the shipper, useful for label or shipment lookup.
LineItem (status response)
Path: Orders[].LineItems[]
Field
Type
Required
Description
LineItemName
string
No
Display name of the item.
Requested
integer
No
Quantity requested.
Received
integer
No
Quantity received.
BackOrdered
integer
No
Quantity on back order.
Shipped
integer
No
Quantity shipped.
Damaged
integer
No
Quantity damaged.
ArtNotReceived
boolean
No
Artwork not received.
ArtBeingProcessed
boolean
No
Artwork is in processing.
WaitingForApproval
boolean
No
Awaiting approval.
OnHold
boolean
No
On hold status.
DateToShip_Orig
string
No
Original ship date (Microsoft JSON format).
DateToShip
string
No
Current ship date (Microsoft JSON format).
DateArtCompleted
string
No
Artwork completion date (Microsoft JSON format).
ReceivingHistory
array|null
No
Receiving events for the line item, null when none.
IsShippable
boolean
No
True if the line item can be shipped.
LineItemID
integer
No
Line item identifier.
IsScheduled
boolean
No
True if the line is scheduled in production.
Invoice Status (response)
Path: top-level invoice status fields
Field
Type
Required
Description
OrderID
integer
No
Internal order identifier.
CustomerID
integer
No
Customer identifier.
IsInvoiced
boolean
No
Whether the order has been invoiced.
IsCanceled
boolean
No
Whether the order has been canceled.
ShippingTotal
number
No
Total shipping charges.
DecorationTotal
number
No
Total decoration charges.
GarmentTotal
number
No
Total garment charges.
Services
number
No
Service charges subtotal.
Total
number
No
Grand total for the invoice.
AmountDue
number
No
Outstanding balance.
AmountPaid
number
No
Amount already paid.
AmountCredited
number
No
Credits applied.
AmountDebited
number
No
Debits applied.
DateInvoiced
string (ISO 8601)
No
Invoice creation timestamp.
LineItems
array
No
Collection of invoiced line items.
Note: Required status may vary based on usage context. See full
documentation sections for detailed rules.
Version 2.0 Endpoint Responses
These response models cover the Version 2.0 pricing, design creation, and lookup endpoints. For POST endpoints, ResponseSummary uses the shared model documented above.
Whether the product style needs additional disambiguation. Prefer the returned Mill or exact ProductID; use VendorName only if the match is unique.
Sizes[]
array<string>
Per result
Available sizes.
Colors[]
array<string>
Per result
Available colors.
Locations GET response
Field
Type
Required
Description
ID
integer
Per result
Location identifier.
Name
string
Per result
Canonical location name.
Description
string
Per result
Readable location description.
Aliases[]
array<string>
Per result
Recognized aliases.
Ship Methods GET response
Field
Type
Required
Description
Id
integer
Per result
Ship method identifier.
Name
string
Per result
Readable ship method name.
Abbreviation
string
Per result
Value used as ShipMethodAbbreviation.
VendorName
string
Per result
Carrier or vendor name.
STANDARD API/Examples and reference
Endpoints & Lookup Lists
Direct and Cloud are both documented.
For supported operations, choose the matching URL and authentication. Cloud IO can queue accepted Order Creation requests during a Dubow Integration outage.
Use this section as the master endpoint index. Every supported JSON operation is listed with its HTTP method, complete Production or Test URL, and a link to its detailed field documentation.
Use the complete URL
Do not submit only a route such as /v1/products or json/products. Select the correct environment and use the complete URL shown below. Production and Test credentials and data are isolated.
Test and Production use different data and credentials. Never mix a Test URL with Production credentials or Production callback URLs.
Cloud IO API URLs
Cloud IO uses /v1/ routes. Accepted Cloud Order Creation requests are queued during an Integration service outage and automatically forwarded when connectivity returns. See Direct vs Cloud IO for authentication and retry guidance.
Cloud Order Creation requires the environment-specific customerToken supplied by Dubow IT. Follow the detailed endpoint section for the request body expected by each additional Cloud operation.
JSON Lookup Lists
Use these JSON lookup endpoints to retrieve available products, locations, and shipping methods. Add supported query parameters to narrow the results.
Quick answers to common questions about requests, order status, artwork, shipping, and error handling.
How do I authenticate?
Direct Integration uses Authorization.UserID and Authorization.Password in the JSON body. Cloud IO Order Creation requires a customerToken provided by Dubow IT. See Authentication and Direct vs Cloud IO.
What does [] mean in field names like
Orders[].OrderID?
It indicates “each array item.” See the global Notation note near the top of
the API Reference for details.
Why are some dates like /Date(1757566800000-0500)/ and others ISO
8601?
Line-item dates use Microsoft JSON format, while tracking timestamps use ISO 8601.
See the Date formats note and UniqueTrackingNumbers.
My Order Status response has UniqueTrackingNumbers empty. Is that
normal?
Yes, until parcels are created. Check Orders[].ShippingStatus and
Orders[].OrderStatus. When shipments exist, UniqueTrackingNumbers[] will include
objects with TrackingNumber, DateShipped,
ShipMethodName, and ShipperReference.
How do I choose a ship method?
Look up abbreviations using the Ship Methods JSON endpoint, then set
ShipMethodAbbreviation on each Manifest. See Ship Methods for the full URL, filters, and response fields.
Can I submit a line item without designs?
Yes, if NoDecoration is true. Otherwise provide
Designs[] with IntegrationColorway. See Designs for required/conditional fields.
How do I add name or number personalizations?
Use Customizations[] inside Designs, including
TextLines[]. See Customizations for
the exact fields.
Do you queue requests during downtime?
Requests to the standard API during an outage return errors and are not queued. Use
the Cloud IO Order Creation endpoint for resilient submission. A valid customerToken from the
Dubow IT team is required, included in the JSON body as customerToken.
See Direct vs Cloud IO.
How are errors returned?
Business-rule errors may be returned with HTTP 200 but with
ResponseSummary.IsSuccess = false and entries in Errors[].
See Error reference and HTTP status codes.
Where can I retrieve product, location, and ship method references?
Use the filterable JSON endpoints under JSON Lookup Lists. Each detailed endpoint section includes complete Production and Test URLs, accepted query fields, and response examples.
Will my webhook payload match the Order Status response?
Yes, when you include OrderStatusNotificationUrl during Order Creation,
the webhook payload mirrors the Order Status response for the same PO. See the Order Status tables.
STANDARD API/Rules and support
What's new
Documentation Changelog
Customer-facing API documentation updates, including new endpoints, request fields, and integration tools.
API version: 2.0. Documentation revisions are tracked separately from API releases.
November 2026
API tools and troubleshooting
Invoice Status requests use json/orders/invoice. Expanded the error guide with decoration method, imprint location, product, and shipping guidance. Improved the JSON Builder layout, including a more compact order form, a clearer preview, and easier access to endpoint URLs.
October 30, 2026
Endpoint and support guidance
Added a clearer Direct vs Cloud IO guide, made the order submission URLs easier to find, added direct contact information for API support, and expanded the searchable Field Finder across the documentation.
October 26, 2026
New layout and easier tools
Reorganized the guide into separate topics, improved mobile navigation, and expanded the JSON Builder. Added examples for using VendorName to identify a product, and documented ShippingCost and HandlingCost in Order Status responses.
July 30, 2026
API v2.0 reference
Added documentation for Decoration Pricing, Hard Goods Pricing, Create Design, Products, Locations, and Ship Methods. Expanded Order Status lookup guidance to cover requests using an Order ID or customer PO number.
June 2026
OrderDesk integration guide
Added a dedicated OrderDesk setup guide with inventory and product mapping, artwork fields, shipping rules, and common troubleshooting steps.
May 2026
JSON Builder and getting-started resources
Introduced the JSON Builder, clearer request examples, a preflight checklist, and improved error guidance to help customers prepare and troubleshoot integrations.
Earlier updates2025
2025: Introduced the online API guide and expanded documentation for webhooks, Cloud authentication, order status, tracking, shipping methods, and full order examples.
Documentation originally developed by Renato Cordeiro and Jake Scherfenberg.
DUBOW API TOOLS
JSON Request Builder
Build a sample request and preview the output as you edit.
Local preview only
LIVE OUTPUT
Generated JSON
Your example updates as you edit.
Direct integration.dubowtextile.comCloud IO io.dubowtextile.comURLs & authentication notes below
REQUEST BODY
Click Generate JSON to create a sample payload.
Endpoint URLsDirect and Cloud IO production, test URLs
POSTDirect Integration production
Cloud IO production
Cloud authentication may differ. See the Direct vs Cloud IO guide.
Test URLs are for reference. Credentials and data are environment-specific. Cloud Order Creation requires a separate customerToken; the JSON generated here is for Direct Integration authentication.
Guidance & checksExample notes
No API request is made from this page.
Use generated JSON as a starting point and confirm account-specific values before
testing.
