Connector name: Brightpearl (listed in Fivetran docs as Brightpearl Lite)

Table name: PRODUCT and ORDER_DETAIL. Ideally as new child tables, PRODUCT_CUSTOM_FIELD and ORDER_CUSTOM_FIELD, plus a metadata table for each listing the field definitions.

Column to add: Brightpearl custom fields are defined per account, so the field names differ for every customer. Please sync them generically, either:

• as child tables with one row per record per field: product_id / order_id, field_code (e.g. PCF_SEASON), value, and option_id where the field is a SELECT type; or
• as a single JSON column called custom_fields on PRODUCT and ORDER_DETAIL.

Metadata tables (field id, code, name, type, required, options) would let us turn field codes into readable names.

API documentation link:

• Product custom fields (supports batches of product IDs): https://api-docs.brightpearl.com/product/product-custom-field/get.html
• Product custom field metadata: https://api-docs.brightpearl.com/product/product-custom-field-metadata/get.html
• Order custom fields: https://api-docs.brightpearl.com/order/order-customfields/get.html
• Order custom field metadata (separate for sales and purchase orders): https://api-docs.brightpearl.com/order/customfield-metadata/get.html

Use case: we use product custom fields for reporting categorization, launch season, markdown status and product tier, and order custom fields for market. Without them we have to keep this data in a separate spreadsheet, which defeats the point of syncing Brightpearl.