Traide Changelog

The following changes have been made regarding the handling of product attributes:

• To update an attribute, the Manage product template and attributes permission is required.

• To update an attribute's values, the Manage product permission is needed.

• Seller staff can only update the attribute values associated with their seller’s primary contact.

For the full list of deprecations and suggested replacements, see GraphQL API Deprecations and Removals.

Performance improvements​

Updating product attributes is now significantly faster, especially when working with products that have multiple attributes.

Fixed a critical issue affecting payout processing.

Fixed an issue preventing product variants from being created when product-level attributes were present, ensuring proper variant creation workflow.

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.

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.

Default addresses in checkout creation​

When creating a new checkout, the customer's default billing and shipping addresses are now automatically applied, streamlining the checkout process.

Staff user management improvements​

Made several improvements to staff user management:

• Staff members can now be created by upgrading existing customer accounts.
• Deleting a staff member now downgrades them to a customer account instead of removing them entirely.
• The isStaff field and related queries now use a new permission-based logic system for more flexible access control.

Enhanced product publishing controls​

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.

Token validation query​

Added a new query that validates whether an authentication token is still valid, making it easier to check token status before making API calls.

Stripe subscription plan tracking​

Marketplace subscriptions now include plan information from Stripe, providing better visibility into subscription details and tiers.

Stripe Tax refund support​

Added comprehensive refund handling for the Stripe Tax integration, including:

• Automatic tax calculation for refunds
• Support for both full and partial refunds
• Proper handling of declined fulfillment scenarios

Attribute template strategy removal​

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:

• The MANAGE_PRICEBOOKS permission is no longer needed
• ProductFilter.dates field will be removed in a future release
• Various legacy mutations and fields across accounts, apps, checkouts, orders, payouts, sellers, products, and plugins

The Authorize.Net payment integration has been removed. Please migrate to Stripe or another supported payment provider.

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.

Performance improvements​

Updating product attributes is now significantly faster, especially when working with products that have multiple attributes.

Fixed an issue where the system incorrectly detected legacy vendor payouts, which could cause payout processing errors in certain scenarios.