BigCommerce – Gotchas
Create differentiated commerce experiences on the industry’s most versatile enterprise ecommerce solution. about BigCommerce.
3 gotchas across 2 resources
These are connector-specific behaviors and limitations to be aware of when integrating.
Orders2 gotchas
ordersAllThe line_items[].discounts[] array includes every applied_discounts[] entry BigCommerce
returns for the line — both target: "order" (cart-level) and target: "product"
(product-specific) allocations are returned together, with no field that reliably
distinguishes the original discount source. This is the same class of behavior as the
documented Shopify discountAllocations limitation.
ordersOneThe line_items[].discounts[] array includes every applied_discounts[] entry BigCommerce
returns for the line — both target: "order" (cart-level) and target: "product"
(product-specific) allocations are returned together, with no field that reliably
distinguishes the original discount source. This is the same class of behavior as the
documented Shopify discountAllocations limitation.
Products1 gotcha
productsAllOn the list endpoint, the product-level options array is not returned. BigCommerce caps results to 10 per
page whenever product options are requested, which would force slow multi-page fetches. To keep full-page
pagination (up to 200 per page), options are omitted from the list response. Each variant still includes its
concrete selections under variants[].options. To retrieve the full product-level options array, fetch the
product individually via the get-by-id endpoint.