10 March 2025
B2BCustomersOrdersMessages/SubscriptionsGraphQL
You can now assign an Order to another Business Unit. This enhancement helps you reorganize historical orders when you restructure or adopt new Business Unit structures. This action will not trigger any revalidation of the fields or recalculation of the price or discount.
This feature is only available as part of Composable Commerce for B2B and will be subject to additional terms and pricing. To get access to Composable Commerce for B2B, contact the Composable Commerce support team.
Changes:
- [API] Added the Set Business Unit update action to Orders API.
- [API] Added the Set Business Unit update action to Orders Edits API.
- [API] Added the OrderBusinessUnitSet Message.
- [GraphQL API] Added the following types to the GraphQL schema:
OrderBusinessUnitSet
,SetOrderBusinessUnit
,SetStagedOrderBusinessUnit
,SetStagedOrderBusinessUnitOutput
. - [GraphQL API] Added the
setBusinessUnit
input field toOrderUpdateAction
type. - [GraphQL API] Added the
setBusinessUnit
input field toStagedOrderUpdateAction
type.
The following changes were introduced in terms of GraphQL SDL:
extend input StagedOrderUpdateAction {
setBusinessUnit: SetStagedOrderBusinessUnit
}
extend input OrderUpdateAction {
setBusinessUnit: SetOrderBusinessUnit
}
type OrderBusinessUnitSet implements MessagePayload & OrderMessagePayload {
businessUnit: KeyReferenceInput
oldBusinessUnit: KeyReferenceInput
type: String!
}
input SetOrderBusinessUnit {
businessUnit: ResourceIdentifierInput
}
input SetStagedOrderBusinessUnit {
businessUnit: ResourceIdentifierInput
}
type SetStagedOrderBusinessUnitOutput implements StagedOrderUpdateActionOutput {
type: String!
businessUnitResId: ResourceIdentifier
}