orders_createAPI call to create a new order, create a new customer, and process the order’s payments in a single call. If your campaign flow requires that a customer be created first, or that a cart be populated with products before the checkout and order placement event, you may use users_create and/or carts_create APIs.
stockrecord_id, rather than using the optional
orders_createwill create the customer at the same time as creating a new order.
idhere. You will then not need to define addresses. In that case, instead set parameters
use_default_billing_addressto = true.
shipping_codecorresponding to the store’s configured shipping methods, which will apply the corresponding shipping cost to the order.
funnel idfor each unique campaign, which will roll up to various reports in 29 Next. Create each unique Funnel in the Dashboard Funnels section, even for externally hosted campaigns, to assign an ID to each funnel for use in this source attribution field. Again, this helps to attribute the unique source funnel to reports for easier data egmentation and analytics.
orders_createAPI calls, you should pass the Everflow click ID as the
everflow_transaction_idinto source attribution metadata. The system will recognize that value and pass it back to the Everflow postback URL on order events.
payment_return_urlin API calls under the
payment_return_url(e.g. standard bankcard transactions) there is no harm in including it in the API request anyway.
orders_createAPI for stores with multiple bankcard payment providers, the best practice is to specify a gateway group rather than a single payment gateway.
payment_detailsspecify a payment_gateway_group to use to process the payment on the order.
orders_add_line_itemsAPI call to add post-checkout upsells to a customer’s order.
orders_createis optional, but it is the recommended approach when selling bundles, to properly reflect discounts and incentives in the sales policy of the store.
voucherson the API.
users_createAPI to create a customer and address records before creating a new order. A customer in 29 Next is referred to as a user on the Admin API.
idon a subsequent
orders_createcall. Setting billing and shipping addresses to default (as collected when the customer was created) can bypass friction in the checkout process.