Multiple carts GraphQL

Served by MultipleCartModule on commercetools and MultipleCartModule on medusa.

Each operation has its own page with its arguments, an example and the engines that serve it. The types link to their fields on the multiple carts types page.

Operations

Operation	Description	Served by
`cartCreateNamed`Mutation	Create a cart under a name and switch to it, which is what a new-cart dialog does.	commercetoolsmedusa
`cartDelete`Mutation	Delete a cart.	commercetoolsmedusa
`cartRename`Mutation	Rename a cart	commercetoolsmedusa
`cartSetCurrent`Mutation	Choose which of the caller's carts is the current one, as returned by the cart query.	commercetoolsmedusa

Types

Type	Description
`CartCreateNamedError`Union	Error union for creating a named cart
`CartCreateNamedResponse`Object	Response for creating a named cart
`CartDeleteError`Union	Error union for cart delete
`CartDeleteResponse`Object	Response for deleting a cart
`CartRenameError`Union	Error union for cart rename
`CartRenameResponse`Object	Response for renaming a cart
`CartResult`Object	Paginated result containing carts
`CartSetCurrentError`Union	Error union for cart set current
`CartSetCurrentResponse`Object	Response for choosing the current cart
`CartStatusType`Enum	Whether a cart is in use

Fields on other types

This domain adds these fields to types that another domain defines.

`BusinessUnit`

Field	Type	Description
`carts`	`CartResult!`	Every cart in this business unit the caller is allowed to see, which includes colleagues' carts where their role permits it, most recently touched first. Active carts only unless status asks for archived ones too.Arguments: `page`, `pageSize`, `status`

`Cart`

Field	Type	Description
`name`	`String`	Buyer-given name, to tell one cart from another. Null until a cart is named.
`defaultName`	`String`	What to call the cart while it has no name: its first product, then a plus and the number of further products, such as "Accuboormachine + 2". Language-neutral, so a storefront needs no wording for it. Given whether or not the cart is named; null for an empty cart, where a storefront shows its own label.
`previewImages`	`[ProductImage!]!`	Images of the cart's first products, one per line in the order they were added and none repeated, so a cart list shows what each cart holds. Add-ons are left out, as is a line without an image. At most 10, whatever the limit asks for; empty for an empty cart.Arguments: `limit`
`owner`	`Customer`	The person whose cart this is. Null for a guest cart, which belongs to a session rather than to anyone.
`status`	`CartStatusType!`	Whether the cart is in use or archived. A cart nobody has touched for 60 days, or the period the service configures, is archived: it leaves the unit's cart list unless that is asked for. The caller's current cart is never archived, so choosing one with cartSetCurrent makes it read ACTIVE.