Production Tenant Features
There are no features targeted for your production tenants.
Production Sandbox Features
Order Management Functionality
- Shopper Notifications: Updates have been made to the SMS notifications used in the BOPIS fulfillment flow. In this flow, customers receive notifications that customers receive when their order is ready for pickup as well as reminders if they do not pick it up within a certain time frame. These notifications now include links to landing pages based on those used in Curbside, which allow the customer to indicate that they are on their way to the pickup location as well as that they have arrived and are preparing to walk into the store. When the shopper clicks either of these buttons (“I am on my way” and “I am here,” respectively), an appropriate notification is triggered to the fulfillment location that updates store associates about the customer’s status. This allows them to anticipate the customer’s arrival at the store and ensure they are prepared to quickly and efficiently hand over the pickup order.
- Searchable Locations: The FFUI’s location selector, used to determine the shipments displayed in the UI based on the location they are assigned to, was difficult to use if the user had access to more than 20 locations. Enhancements have been made so that the dropdown options are sorted by name and able to be searched by name, allowing the user to select their current location more quickly.
- Return Restock Location: If a returned item is restockable, then it is now possible for the customer service representative to select the restock location when processing the return. When a returned item is restocked, its quantity will be added back to the available inventory at that location. This location defaults to the return location selected in the site settings, but the CSR can change this selection for the particular return. However, note that this is only supported for locations that use Kibo’s inventory management and any other locations will not be included in the restock options.
- Additional Shipment Fields: A new field, assignedLocationCode, has been added to the Shipment object model in all order management API calls. This optional field is always a string value and tracks which location should handle the shipment, which is usually the same as fulfillmentLocationCode – however, it will change to reflect the receiving location code when a transfer shipment is shipped. This data will now be returned with the shipment data in API responses.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Sandboxes | Previously, shipments in the Backorder and Customer Care state were able to be rejected via the Reject Shipment API call. This has been corrected so that a request to reject these shipments receives an error instead, as well as the same case for the Reject Items API. |
| Targeted for Production Sandboxes | The External Order ID was not always being displayed on the fulfiller dashboard nor the shipment details page. This has been added so that any existing external order numbers are properly exposed. |
| Targeted for Production Sandboxes | Locations were unable to be deleted from order routing custom lists as they would reappear after refreshing the page, in addition to the Location ID being mistakenly displayed alongside the location’s name. This has been corrected to allow proper deletion of locations from lists and show only their name. |
| Targeted for Production Sandboxes | Some orders were placed in the Processing status immediately after being Accepted, when they should have remained at Accepted until a shipment has been fulfilled. This has been corrected so that the order-level statuses better reflect the current shipment-level statuses. |
| Targeted for Production Sandboxes | The http.storefront.routes Arc action only returned blank content when a POST call was made with an application/x-www-form-urlencoded body. This has been fixed so that the action better supports non-JSON request bodies, though it is important to note that the output will always be JSON. |
| Targeted for Production Sandboxes | Making a Reject Shipment call via API to reject backordered and customer care shipments was accepted by the API, despite this not being the intention. An error message has been added to the API responses for these cases, which states that backorder and customer care shipments cannot be rejected. |