Skip to content

Changelog

  • Return parent product ID and name on Partner API variant responses, with company and location display name overrides applied to the parent name when enabled.
  • Add asset order and priority settings to variant asset configuration in partner location config responses
  • Fix asset config lookup so variants with no type fall back to the shared default config, and an empty partner entry is treated as absent
  • Add ordering and priority for variant asset configurations in partner location configuration.
  • Internal dependency updates and stability improvements
  • Improve SKU asset resolution to return an approved image for each configured type, falling back to cross‑bucket or any sibling assets when needed.
  • Add location‑specific cannabinoid hydration that respects partner integration configuration and allowed fields.
  • Convert cannabinoid values only when sourced from BPD, preserving customer‑sourced overrides.
  • Enable merging of cannabinoid overrides in partner configuration.
  • Refine asset ranking to prioritize assets by barcode, upload recency, and unique identifier.
  • Restore fallback asset sharing across sibling variants, enabling assets to be retrieved from sibling barcodes when primary assets are unavailable.
  • Update asset type mapping.
  • Classification field in PartnerVariant is deprecated in favor of StrainType. Both fields are provided for backwards compatibility.
  • Add partner configuration level overriding for location settings
  • Hydrate partner API display names from company and location display attributes
  • Hydrate product characteristic fields on partner API variant objects
  • Add StrainType field to PartnerVariant model and deprecated Classification
  • Increase maximum size for large partner images to 1920 pixels
  • Dynamically filter partner variant assets based on config values
  • Allow nullable locationId for BatchGetVariants requests
  • Initial release of Webhooks for BPD updates
  • Healthcheck endpoint
  • Update Partner Integration endpoint
    • Use this endpoint to configure webhook delivery
  • Return company-specific configuration for your partner
    • While this is returned, it isn’t exposed to end-users. The data will be identical for all companies at the moment, but in a future release, this information will flow through live data.
  • Initial bug fixes and stability improvements

For detailed information about each release, including migration guides and breaking changes, please refer to the respective version documentation.

For questions or issues related to changelog items, please contact us.