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.
General
- Provide singular technical point of contact for integration-related work, issues, and troubleshooting.
- Provide the ability to test the integrations using JOOR’s Sandbox Account.
- Send JOOR the header (including endpoint URI) and body (XML/JSON) details of specific API requests to help troubleshoot issues.
- Provide interface with integration settings on the ERP accessible by the brand.
- Process and display REST API responses to users to allow for troubleshooting errors.
- Provide training to brand on ERP integration process with JOOR.
- Trigger all integrations automatically via a set schedule and manually on demand.
- Ability to store multiple API tokens, if account is split to multiple JOOR profiles -- usually per division or company.
Styles
- Create, update, and delete styles.
- Support multiple price types and currencies for wholesale and retail prices.
- Deactivate sizes.
- Delete colors.
- Split styles in JOOR by brand’s desired method (i.e. colors, fabrication, silhouette, etc.).
- Create and assign custom style fields (style tags).
- Send JOOR Categories when creating styles.
- Send casepack sizes. Note: Casepacks need to be setup in JOOR before sending.
- Use standard ISO 3-character currency codes.
- Send the same price type currencies and labels for styles and customers.
- Allow users to manually create linesheets in JOOR (using the delivery_overwrite field).
- Create linesheets in JOOR based on brand’s criteria (season, delivery, etc.).
- Exclude colors from linesheets per season.
- Drop styles from linesheets.
Inventory
- Load inventory using Color, Size, and Style ID or Style Identifier if splitting styles by data other than Style Number.
- Provide option for brand to send all inventory (Overwrite) or updates only (Update).
- Support multiple warehouses and availability dates (Immediate and future).
- Send inventory for casepack sizes.
Images
- Send images as non-password protected URLs.
- Send style, color, and swatch images to JOOR as desired by brand.
Connections
- Utilize the Bulk Connections endpoint to create and update customers.
- Create Doors based on shipping addresses.
- Assign Discounts at the Order or Item level.
- Assign warehouses to customers.
- Assign Sales Reps to customers.
- Use standard ISO 3-character currency codes.
- Send the same price type currencies and labels for styles and customers.
Orders
- Import orders from JOOR, perform a valid import to ERP, and mark the order as “Exported” in JOOR using sync=1 parameter.
- Store JOOR’s Order ID for reference in the ERP.
- Import the same order more than once to overwrite data in ERP.
- Import all style, customer, and order data from JOOR.
- Import Order and Line Item level discounts.
Updated 12 months ago