: Staging
: Production
💎 Changed
Performance improvements
Updating product attributes is now significantly faster, especially when working with products that have multiple attributes.
Changelog
We regularly update our product and API while providing detailed notes on each release. We first release to staging, then to production about a week later. Learn more about our release process.
: Staging
: Production
Updating product attributes is now significantly faster, especially when working with products that have multiple attributes.
: Staging
: Production
Fixed a critical issue affecting payout processing.
: Staging
: Production
Fixed an issue preventing product variants from being created when product-level attributes were present, ensuring proper variant creation workflow.
: Staging
: Production
Fixed an issue where the marketplace's fulfillment settings could incorrectly override individual seller preferences, ensuring each seller's fulfilled_by_marketplace configuration is properly respected.
: Staging
: Production
Fixed an issue where the is_staff field in certain input mutations was not being properly validated, which could lead to unexpected behavior when updating user permissions.
: Staging
: Production
When creating a new checkout, the customer's default billing and shipping addresses are now automatically applied, streamlining the checkout process.
Made several improvements to staff user management:
isStaff field and related queries now use a new permission-based logic system for more flexible access control.Products with variant attributes now require at least one variant before they can be published or made available. When a product's publish status changes, all associated variants are automatically updated to match.
Added a new query that validates whether an authentication token is still valid, making it easier to check token status before making API calls.
Marketplace subscriptions now include plan information from Stripe, providing better visibility into subscription details and tiers.
Added comprehensive refund handling for the Stripe Tax integration, including:
Removed the deprecated attribute template strategy system. Attributes now use a simplified locking mechanism that provides better control over attribute modification.
Fixed an issue where the is_locked attribute default value was not being set correctly based on the template strategy.
Fixed a permissions issue where staff members could view order metadata they shouldn't have access to. Only relevant staff with appropriate permissions can now view order metadata.
Fixed validation logic for fixed-amount refunds to ensure accurate refund processing.
Deprecated several API fields and permissions as part of ongoing platform improvements:
MANAGE_PRICEBOOKS permission is no longer neededProductFilter.dates field will be removed in a future releaseThe Authorize.Net payment integration has been removed. Please migrate to Stripe or another supported payment provider.
: Staging
: Production
This feature automatically applies the user's default saved shipping and billing addresses during the checkout process on the storefront.
Fixed an issue with the validation for fixed amount refunds. Learn more about refunding fixed amounts here.
For the full list of deprecations and suggested replacements, see GraphQL API Deprecations and Removals.
: Staging
: Production
Updating product attributes is now significantly faster, especially when working with products that have multiple attributes.
: Staging
: Production
Fixed an issue where the system incorrectly detected legacy vendor payouts, which could cause payout processing errors in certain scenarios.
: Staging
: Production
Fixed an issue where the marketplace fulfillment setting was not properly respecting the seller's fulfilled_by_marketplace configuration in certain scenarios.