Next Integration

Next Setup Guide, this page provides step-by-step guidance on obtaining credentials, which are essential for the setup process.

Last updated 24 days ago

What is Next

Next is a British multinational clothing, footwear, and home products retailer that operates online and through brick-and-mortar stores. The company offers a wide range of products, including men's, women's, and children's clothing, footwear, accessories, and home goods such as furniture, bedding, and decor. Next is known for its focus on quality and style, offering a mix of classic and contemporary designs at affordable prices. The company has a solid online presence, a user-friendly website and a range of delivery options, including next-day and nominated-day delivery. Next also operates stores throughout the UK and Ireland, allowing customers to shop in-person or online. Overall, Next is a popular and well-respected retailer that offers customers a wide range of high-quality products in the UK and beyond.

Obtaining your API Keys from Next

You'll need to contact their customer service team to obtain your API key from Next. The API key is a unique identifier that provides access to Next's system, allowing us to retrieve data and perform actions on behalf of your customers. With the API key, you can enable features such as order tracking, inventory management, and more. To contact Next's customer service team, visit their website or call their support hotline. They'll be able to guide you through obtaining your API key and answer any questions.

Installing the Next Sales Channel

To add the Next sales channel to your Neuro account, kindly adhere to the following steps:

Access your account and go to the left side of the screen. Click the "Stores" button.
If you already have a store, click "View Store" on the right side of the screen to access it.
To edit an existing store, click the edit button on the right side. If you need to create a new store, click "+ ADD" above, name it, and use the edit button to make changes.
Click "+ ADD" in the channels section to begin the installation.
A window will appear in the centre of the screen. Choose "Next" from the available channels list.
Provide the required information:
- Channel Name: In the field provided, you can enter any name. However, it is recommended to choose a name that has meaning to you, such as "Next," as it will serve as an apparent reference for the source of the order in the future.
- Channel Username & Password: Please create a username and password in the corresponding fields for basic authentication purposes in the "create order" endpoint.
- API User & Key: For these fields, please insert the credentials provided by Next.
After filling out the fields, customise other options, then click "Save" in the bottom-right corner.
You'll be back in the recently installed channel. Activate it at the top of the screen using the "Is Active" button.

Congratulations! You've successfully set up your Next sales channel on Neuro.

You can now sell products on Next and manage orders from your Neuro dashboard.

Click to Maximise the Video.

Order Creation

Orders are sent into the platform by posting to a single endpoint, POST /api/v1/nextChannels/createOrder, which accepts a batch of orders in one request and creates a confirmation order for each one.

Endpoint and authentication

Send a POST request to /api/v1/nextChannels/createOrder with a Content-Type: application/json header.

Authentication uses the channel username and password configured on the Next sales channel, passed in the Authorization header.

The credentials are sent as plain text, not Base64 encoded. Despite the Basic prefix, the value must be the literal username:password string. A standard Base64-encoded Basic header will be rejected.

POST /api/v1/nextChannels/createOrder HTTP/1.1
Host: <your-host>
Authorization: Basic myusername:mypassword
Content-Type: application/json

The Basic prefix is optional. Sending the header as just myusername:mypassword works identically.

Request payload

The body is a single object with one key, Orders, holding an array. Each entry is one order, and each order carries its own Items array. Several orders can be sent in one request.

{
  "Orders": [
    {
      "ID": "NX-1000045",
      "Destination": "NextRDC",
      "Currency": "GBP",
      "DateTimeStamp": "2026-09-22 10:15:00",
      "Items": [
        {
          "ItemID": "1",
          "EAN": "5051234567890",
          "BrandSKU": "CH-LAPTOP-001",
          "Quantity": 2,
          "Price": 2599.98,
          "title": "Dell XPS 13 Laptop"
        },
        {
          "ItemID": "2",
          "EAN": "5051234567891",
          "BrandSKU": "CH-PHONE-001",
          "Quantity": 1,
          "Price": 899.99,
          "title": "iPhone 15 Blue"
        }
      ]
    }
  ]
}

The full request as a curl command:

curl -X POST 'https://<your-host>/api/v1/nextChannels/createOrder' \
  -H 'Authorization: Basic myusername:mypassword' \
  -H 'Content-Type: application/json' \
  -d @order.json

Order-level fields

Three fields are compulsory on every order. A request missing any of them is rejected in full, and no orders in the batch are created.

Field	Required	Type	What it sets
`Orders`	Compulsory	Array	The batch of orders. Must contain at least one order.
`Orders[].ID`	Compulsory	String	The order reference held against the order. Must be unique per channel.
`Orders[].Destination`	Compulsory	String	The delivery destination code. Resolves the delivery name and address. See Integration notes.
`Orders[].Currency`	Compulsory	String	The order currency, as a three-letter code such as `GBP`.
`Orders[].DateTimeStamp`	Optional	String	The order date. Defaults to the time the request is received if omitted.
`Orders[].Items`	Compulsory	Array	The order lines. Must contain at least one item.

Item-level fields

Each entry in Items describes one order line. Three fields are compulsory.

Field	Required	Type	What it sets
`ItemID`	Compulsory	String	The line sequence number, used to order the lines.
`EAN`	Compulsory	String	The product barcode. Must be supplied, but is not currently stored against the line.
`BrandSKU`	Compulsory	String	The product SKU. Used to match the line to a product.
`Quantity`	Optional	Integer	The quantity ordered. Defaults to `0` if omitted.
`Price`	Optional	Decimal	The line value. Defaults to `0` if omitted. See Integration notes for how this feeds the order total.
`title`	Optional	String	The product name shown against the line. Defaults to empty if omitted. Note the lower-case spelling.

Although Quantity and Price are optional, omitting them creates a line with a quantity and value of zero. Send both on every line unless you have a specific reason not to.

Responses

A successful request returns 200 with the created orders in data.

{
  "status": true,
  "data": [ ... ]
}

Status	Meaning	What to do
`200`	Orders created.	Nothing. The `data` array holds one entry per order created.
`401`	Credentials did not match an active Next channel.	Check the username and password, and confirm the header is plain text rather than Base64.
`422`	A compulsory field is missing or malformed.	Read the `errors` object, which names each failing field. No orders in the batch were created.
`429`	Rate limit reached.	Back off and retry.

Integration notes

Four points catch most integrations out.

Field names are case sensitive. Every field uses PascalCase except title, which is lower case. Sending Title is accepted but silently produces a line with no product name.

Destination currently resolves one code, NextRDC. That code maps to the Next Retail Ltd collection address. Any other value is accepted, but the order is created with the raw code as the delivery name and no address lines against it. Ask us to configure a code before you start sending it.

Price is not multiplied by Quantity. The order total is the sum of the Price values across the lines. Send the extended line total in Price, not the unit price, or the order total will be understated.

Orders arrive as confirmation orders. They are created ready for acknowledgement rather than as despatch-ready sales orders, and follow the standard confirmation order workflow from that point.

For additional support, contact the Neuro Support Team.

Was this helpful?

Still need help? Share an idea