Best Practices

The following is a list of best practices for JOOR's Brand API. We recommend implementing these functional and technical capabilities while building your API integration with JOOR for the best possible user experience.


  1. Provide a singular technical point of contact for integration-related work, issues, and troubleshooting.
  2. Provide the ability to test the integrations using JOOR’s Sandbox Account.
  3. Send JOOR the header (including endpoint URI) and body (JSON) details of specific API requests to help troubleshoot issues.
  4. Provide an interface with integration settings on the ERP accessible by the brand.
  5. Process and display REST API responses to users to allow for troubleshooting errors.
  6. Provide training to brand on ERP integration process with JOOR.
  7. Trigger all integrations automatically via a set schedule and manually on demand.
  8. Ability to store multiple API tokens, if an account is split into multiple JOOR profiles -- usually per division or company.

v4 API Best Practices

JOOR v4 API is relatively new. Our QA team has thoroughly tested it; however, please refrain from pushing our limits and follow the below guidelines when making requests.

  • Use unitary requests whenever possible; yes, v4 is a bulk API; however, it's much easier for JOOR and the client support teams to troubleshoot a request with a single object.
  • When sending multiple requests to the same endpoint, please wait for the response to the previous request before sending a new one.


  1. Create, update, and delete styles.
  2. Support multiple price types and currencies for wholesale and retail prices.
  3. Deactivate sizes.
  4. Delete colors.
  5. Create and assign custom style fields (style tags).
  6. Send JOOR Categories when creating styles.
  7. Send case pack sizes. Note: Casepacks need to be set up in JOOR before sending.
  8. Use standard ISO 3-character currency codes.
  9. Send the same price type currencies and labels for styles and customers.
  10. Allow users to manually create linesheets in JOOR (using the delivery_overwrite field).
  11. Create linesheets in JOOR based on the brand’s criteria (season, delivery, etc.).
  12. Exclude colors from linesheets per season.
  13. Drop styles from linesheets.


  1. Load inventory using Color, Size, and Style ID or Style Identifier if splitting styles by data other than Style Number.
  2. Provide an option for a brand to send all inventory (Overwrite) or updates only (Update).
  3. Support multiple warehouses and availability dates (Immediate and future).
  4. Send inventory for case pack sizes.


  1. Send images as non-password protected URLs.
  2. Send style, color, and swatch images to JOOR as desired by the brand.


  1. Utilize the Bulk Connections endpoint to create and update customers.
  2. Create Doors based on shipping addresses.
  3. Assign Discounts at the Order or Item level.
  4. Assign warehouses to customers.
  5. Assign Sales Reps to customers.
  6. Use standard ISO 3-character currency codes.
  7. Send the same price type currencies and labels for styles and customers.


  1. Import orders from JOOR (perform a valid import to ERP)
  2. Store JOOR’s Order ID for reference in the ERP.
  3. Update order shipping data on JOOR.
  4. Update order payment data on JOOR.
  5. Update order line item data on JOOR if it changes on the ERP.
  6. Update customer order data on JOOR if it changes on the ERP.
  7. Import the same order more than once to overwrite data in ERP.
  8. Import all style, customer, and order data from JOOR.
  9. Import order and line item level discounts.