Release Notes

The new Webhook feature allows users to subscribe to supported order events. This self-service pub/sub feature allows users to specify a target URL and receive a notification (throttled at up to 10 events per second) every time an event occurs, such as an order created. This makes it easy to integrate fabric OMS with any integration platform of choice. This feature is currently in closed beta for new customers only.

The new File Group Export endpoint in the OMS API makes it easier to bulk export inventory data to third-party data platforms, supporting use cases such as business intelligence analysis.

In the fabric OMS API, merchants can integrate with the Inventory True Up endpoint to update data with Inventory Overlays. 

True Up makes it easy for merchants to integrate SAP store inventory or Manhattan WM with fabric OMS. It also makes it easy for merchants to migrate from Manhattan Active or ATG to fabric OMS for modern enterprise distributed order management (DOM) system architecture that is API-first and cloud-native.

In the fabric OMS Copilot integration, it’s now possible for users to update all fields in their location data to manage inventory availability and fulfillment logic settings.

fabric OMS has released an Inventory Aggregation Engine that calculates inventory availability across multiple locations by specifying product and location attributes as aggregation criteria. This improved method creates more reliable and accurate inventory data for easier sales conversions.

Return and cancellation feature users to create policies for customers who want to return orders they’ve received, or cancel orders before they ship. These policies can be configured based on order status and even set up to trigger automatic refunds.

In addition, custom attributes now appear along with a customer’s order in the Order Detail page to help brands their customers. For example, if a customer chooses gift wrapping as a part of their order, that addition will be shown on the Order Details page for more efficient order management.

Inventory availability is now easier to manage in the OMS interface. OMS users can create inventory positions in Copilot and then use them to update inventory quantities. Location capabilities have also been expanded. Users are no longer limited to the standard attribute set, and can create and update new Location attributes to be referenced in order fulfillment and inventory availability rules.

Thanks to the latest EventBridge backend changes, creating a new product in PIM now automatically triggers creation of a new product in OMS. The event is detected by our handler on copilot-business-layer allowing us to take the SKU, itemID, and title and upsert the information via the inventory service. 

Merchants can create Service-Level Agreements (SLAs) that promise delivery windows to the customer in the Settings menu of OMS with the new Fulfillment, Shipment, and Delayed Order SLA rules. 

Also new to the Settings menu are Returns and Cancellations policies as a validation step whenever a customer requests a return or cancellation. A related update allows you to use the filter feature on the Orders menu to sort orders by returns and cancellations.

In addition, the Orders and Inventory menus now feature a Bulk Upload option to add multiple items from a CSV file. If there are errors in the file you upload, OMS will highlight the errors in the file and allow you to download it so that you can make corrections.

New changes in Copilot include a new Settings page with tabs “Custom Attributes,” “Fulfillment,” “Shipping & Carrier.”

In the Custom Attributes tab, merchants can create attributes to surface for customers to select optional offerings such as Gift Wrap, Gift Message, flat fulfillment/white glove services for free or additional cost at item or order level.

In Fulfillment, merchants can choose Fulfillment Methods at the item or order level to be fulfilled from locations such as Store (BOPIS, Curbside) and Warehouse (3PL, Owned, Dropship). Fulfillment Priority can now be managed to choose either “Always ship from closest” or the first fulfillment method available in order of priority.

In Shipping & Carrier, merchants can create and update custom business rules and settings for shipping and delivery SLAs, updating the delivery SLA estimates, freight restrictions, and related carrier information at the item or order level.

Bulk import of CSV files is now provided for orders. A downloadable template is also available for easier import.

Design updates to the OMS UI enable easier navigation, status views for orders and warehouse details, and an improved order filtering experience. 

New settings for checkout options, fulfillment rules, and shipping are now available.

Now you can give customers the option to split a payment across multiple payment methods such as Gift Cards, Loyalty Points, PayPal and Credit/Debit Cards. You can also authorize customer payment methods and store payment details using the payment gateway of your choice. Learn more about this feature in the blog post announcement.

Split Payments

fabric supports split payments between these payment methods:

• Gift Card

• Loyalty Points

• and Credit/Debit Cards

• Apple Pay

• Google Pay

• PayPal

Multiple Payment Gateways

Customers can make full or partial payments through the payment gateway of your choice. fabric supports the following payment gateways:

• Stripe

• Authorize.net

Using fabric Copilot OMS, merchants can now import tracking IDs in Bulk as a CSV to move orders to "shipped" status.

JSON Web Token (JWT) is now mandatory for the following Wishlist APIs: 

• POST /api-cart/wishlist - Add item to wishlist.
• DELETE /api-cart/wishlist/user/{userId}/item/{itemId} - Remove item from wishlist.
• GET /api-cart/wishlist/user/{userId} - Retrieve wishlist for the specified user ID. 

The response of these APIs using JWT is an object with a user ID and an array of Item IDs.

Note: ‌If JWT is not provided, you will see a 403 error code with the message “Unauthorized User.”

External inventory search

By enabling external inventory search in Co-pilot OMS, you can now get generic items and multiple items by itemId.

This API: /api-inventory/inventory/generic/1000000002?query=itemId endpoint enables you to get generic items by itemid.

This API: /api-inventory/inventory endpoint helps you retrieve details of a single item or multiple items from the inventory by itemid.

Inventory feed API

Users can now be provided with an option to add itemIds on top of the existing options for SKUs. Both SKU and Item ID can be passed together. If the mapping between SKU and Item ID is not correct, the user will see an error "SKU and Item ID do not match." One of the IDs (SKU or Item ID) is mandatory. If both SKU and Item ID are passed, Item ID will be used as a preferred parameter.

You can import inventory items in Bulk as a CSV to upload all the inventory items at once.

POST/api-inventory/inventory/bulk-insert - Through this API endpoint, we enable you to easily update your inventory, in bulk.

Note:

• If an incorrect itemId is passed, you will see the following error message: “Inventory insert failed: Row 2: Cannot find 'itemId' 1100000213.”
• If an incorrect SKU ID is passed, you will see the following error message: “Inventory insert failed: Row 1: Cannot find 'sku' a93120.”

Inventory sync (via Algolia)

This new feature is built for merchants who want their inventory data (Algolia Platform) to be in sync with any inventory updates within the platform. Prior to this enhancement, inventory data was updated in a CRON job that runs every four hours.

Now, we have updated the inventory microservice to invoke the SNS event itemAddUpdateSnsTopic to drive sync whenever inventory changes occur.

Order cancellation by customers and merchants

There are times when orders must be canceled if they were ordered by mistake or the item is out-of-stock, etc. Prior to this release, users could not cancel orders from within Copilot.

Now, customers and merchants can cancel orders directly from Copilot, based on the following criteria:

• The order is placed within 24 hours.
• Order is not shipped.

Order cancellation by customers

Customers can cancel their orders directly from the UI of your e-commerce store. You can configure the cancellation reasons and the corresponding codes to analyze the cancellations.

Example: Customer cancels an order because the “item description is incorrect” and the corresponding cancellation code is 2006. You can analyze all the cancellations associated with 2006, and take corrective steps to resolve any description-related issues.

A new API PATCH / api-order/orders/cancel is introduced to support customer-driven order cancellations. This API is triggered when a customer clicks the Cancel Order button from your site.

Order cancellation by merchants

You can cancel orders directly from the co-pilot UI. You can configure the cancellation reasons and the corresponding code for future reference and analysis. Example: You are canceling an order because the customer’s address isn’t correct, and the reason code is 1003. You can analyze all the cancellations associated with 1003, and take corrective measures to fix the issue at the source.

A new API POST /api-order/orders/bulk-cancel is introduced to support merchant-driven order cancellations. You may cancel a single order or multiple orders in bulk, as per your requirement.

Feature enhancements

Ability to save order filtering criteria

When you apply a filter on the Orders page, the filter criteria are saved, even when you navigate to another page.

Save filter in OMS