BOX NOW Eshop integration: lockers, labels and checkout experience

A BOX NOW integration connects the customer's locker choice with parcel creation and tracking.

BOX NOW offers integration routes for established commerce platforms and a Partner API for custom connections. Official guidance describes OAuth2, separate test and production environments, destinations and delivery requests. Locker selection is part of the order and should retain a stable identifier as well as its displayed address. Cash-on-delivery and cancellation capabilities depend on account eligibility and parcel state. Confirm the terms applicable to the merchant's own agreement before presenting a checkout option. The connector must preserve operational meaning rather than saving only a readable locker name.

At checkout the customer selects an available locker and the choice is stored before the order is created. The connector maps the correct warehouse origin to the destination, prepares a request and preserves the information needed for a shipping label. If the customer changes carrier, an older locker selection should not remain the active destination. Returning to checkout should show the previous choice clearly and revalidate it when appropriate. This avoids orders that specify BOX NOW but lack a usable delivery point, especially after checkout recalculation or a payment-method change.

A duplicate order identifier, expired token or ineligible payment type can block shipment creation. Sending the same payload again is not always the correct recovery. Classify the error, retain the order and tell staff what needs correction. Cancellation should inspect parcel state before changing the store's status. Test and production credentials must remain separate so a checkout experiment cannot trigger an unintended real shipment. Operational logs should show the request relationship and safe troubleshooting information without exposing client secrets or tokens.

A locker is delivery data, not a decorative checkout choice. A BOX NOW connection preserves its identifier and the address shown to the customer. Changing shipping method requires rechecking what remains on the order. Warehouse staff see origin and destination separately so a customer's locker choice cannot be confused with internal configuration. If a valid locker is missing, provide clear guidance before a delivery request is created. Test mobile checkout, returning to the basket and payment-method changes as well as the successful first selection.

An accessories shopper selects a locker on a phone and then changes to home delivery. The order should retain only the active delivery choice. Returning to BOX NOW displays a valid destination rather than a hidden stale value. A payment-method change rechecks relevant rules before submission. Warehouse staff see the actual destination and shipping origin. Create the delivery request from the final order and associate it with a stable reference. Support can then investigate a checkout change without guessing which of several old selections produced the parcel.

Test submission without a locker, carrier and payment changes, an expired token and a repeated request. Expect clear customer guidance and no unintended second shipment. Check environment, origin and the correct PDF label before production. A disallowed cancellation must produce an understandable pending exception. Mobile testing includes returning to checkout and refreshing the page. Staff confirm that the chosen locker remains associated with the order and parcel reference. Test recovery after an uncertain request outcome separately from correcting a genuinely invalid checkout selection.