Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Business State Errors

Business State Errors

Business state errors can occur on POST, PUT and DELETE operations. Errors are returned as Structured Messages with the HTTP status code 409 Conflict.

The following invalid business state errors can be returned.

Message ID Message Fields Example Message Template
cart.item.not.available item-code Item '{item-code}' is not available for purchase.
payment.failed Error occurred when processing payment.
payment.declined Payment was declined.
payment.insufficient.funds Insufficient funds to process payment.
payment.method.expired Payment method has expired.
payment.method.invalid Payment method is invalid.
payment.currency.not.supported Payment currency is not supported by the store.
purchase.cart.is.empty Shopping cart is empty.
purchase.cart.not.purchasable Shopping cart cannot be purchased because one or more items are unavailable.
purchase.item.not.available item-code Item '{item-code}' is not available for purchase.
purchase.item.insufficient.inventory

item-code

Insufficient inventory for item '{item-code}'.
purchase.item.minimum.quantity.required

item-code
minimum-quantity

A minimum quantity of {minimum-quantity} must be purchased for item '{item-code}'.
purchase.missing.shipping.address A shipping address is required.
purchase.shipping.service.level.invalid

shipping-level

Invalid or missing shipping service level '{shipping-level}'.
purchase.user.account.not.active user-id User account '{user-id}' is not active.
profile.email.already.exists email User account with email address '{email}' already exists.
profile.userid.already.exists user-id User account with the user id '{user-id}' already exists.
Warning:

These messages are subject to refactoring in future releases as resources are converted to Helix. Make sure that your client implementation is easy to update as messages are modified, added or deleted.