Service Updates & Release Notes

Learn about new features and bug fixes for Kibo products.

Order Management System

February 20, 2018 — 18.2 Release: Service Update (Early Access)

This is an Early Access draft. Changes may occur up to the time of release. The functionality described here is scheduled for release on February 20th, 2018.

Features

  • Configurable Late Order Queue: The late order queue in the Fulfiller UI previously showed orders that were one day late. This is now configurable to a specified number of days late, which can be changed in the Fulfiller Account Settings. This new option is under the current setting for “Use tabbed order alerts table” and modifies both the tabbed and untabbed versions of the alerts table.
  • Test Order Filter: Previously, there was no way to hide orders sent with a testOrder flag of “true” in the Customer Care and Fulfiller interfaces. A new configuration option has been added to both of these interfaces to hide these flagged test orders, so that they will not appear in order queues or search results.
  • New eCommerce Languages: Several languages were previously non-commerce languages that have now been added as eCommerce languages. Orders can now be accepted in Russian, Japanese, Korean, Cantonese, Mandarin, and Traditional Chinese. These languages can also be set up in catalogs and email notifications.
  • CCUI Appeasements: Improvements have been made to the Customer Care interface functionality for processing appeasements. When an appeasement radio button is selected, the appeasement reason is set to the appropriate default option. For instance, if the “Shipping” radio button is selected then the reason automatically changes to “Shipping Appeasement.” Additionally, there was not a radio button for S&H Tax and this has now been added.
  • Location Data Table: As part of an inventory scalability project to improve the process of getting locations in a network, which previously required JOINing the results of various tables, the information has been consolidated to a single roll-up table. This table represents all locations in the specific network with their attributes calculated from various possible perspectives. This allows location network data to be queried in a simpler and more efficient way. If a catalogID is not provided, it can be queried by qry_mfg_id IS NULL. If a catalogID is provided, query by qry_mfg_id = ?
  • Assembly Messaging: As requested by a particular client, a new type of email notification can be sent to the customer alerting them that their item is being assembled. This is sent after the store has picked the item, and before the order is ready to be delivered or picked up in-store. This will be accompanied by the new FSM state created for item assembly.
  • Service and Physical Items: As part of the same assembly functionality as above, the Create Order 2 API has been updated to allow service items that are dependent on a physical item. Assembly will be the separate service item (designated with the product availability marker for a service) that has a dependency on a physical, deliverable item. Fully mixed orders with independent service and product item types are still not supported.
  • Front-End Product Mapping: Previously, custom product mappings had to be done in the code by Kibo developers. Now, a new front-end webpage has been created in Inventory (/coex/custom-product-mappings) that allows users to efficiently search, create, update, and delete custom product mappings themselves. The existing product mapping settings page has also been updated with a link to the new custom mappings page, and fulfillerIDs on that page now also link to the new page with the relevant fulfiller already queried.
  • Obliterate Inventory Attributes: There was not an existing method for clients to change or delete inventory attributes, but clients who set up this information often did not know what the final attribute set would be. Functionality has been implemented to allow clients to better manage their inventory attributes after set-up. The Inventory Obliterate tool (/coex/delete-all-inventory) can now wipe out the inventory attribute map when all locations for the fulfiller are selected via the checkbox. This will delete all selected attribute entries that are no longer needed.
  • Duplicate Customer Script Update: The script used to clean up duplicate customer records has been updated with a new version, which merges records based on manufacturer prefixes that may have been added or removed after go-live and caused duplicates. The script now takes in the manufacturer prefix to be searched on (a three letter string) and a flag indicating whether to keep prefixed email customer records (TRUE) or plain email customer records (FALSE) . Note that this script does not support having mixed customer records with some manufacturer prefixes and some without. This script is run by Kibo, with the appropriate information provided by the client.
  • Opt-in Associate Notifications: Store associates can now opt in to receive text messages and email alerts for ISPU and return orders coming to their store, which includes information such as where the return originated from (API, CCUI, etc.). Return notifications are sent for not only the creation of a return, but also for each stage of return processing. This opt-in option is accessed in the Fulfiller UI as a check box under Account Information and can be further configured to only receive either text or email alerts, or both. It is defaulted to opt in if both email and phone number for text messages have been provided, and for the provided contact channel if only one is present. These notifications have also been made secure with the ability to store a secret key in the header in the notifications system. This can be set up by Kibo during the notification subscription configuration process.

Bug Fixes: Customer Care

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
NAEditing an order’s shipping address in the CCUI resulted in an error message and incorrect field validation. This has been fixed so that shipping address can be appropriately edited by both KIBO and MFG admins.
NAThe cache delay for custom order data in the CCUI was 2 hours, which meant that customer service representatives could not immediately view custom data added via API. This has been changed to a few minutes, so that order data can be edited sooner when necessary.
NAThere was a lingering issue with currency formatting in the CCUI, as currencies with anything more or less than two digits after the decimal could not be displayed properly. This affected a few known currencies with either zero or three digits after the decimals: JPY, KRW, HUF, and KWD. The currency library has been updated to handle these formats, though there are additional defects with KWD in regards to rounding and browser locales that will be addressed.

Bug Fixes: Core Order Management

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00255037 Due to a rounding error in a particular configuration, the amount refunded for shipping when a single item is returned was 0.01 less than the expected amount. This calculation has been corrected.
00309244 Some onBlocks mobile sites were not displaying product images correctly when the “additional photo” and “color option” settings were changed. This was an issue with a mobile template type that did not update the display image when new selections were made. The JavaScript of these templates have been fixed so that they correctly update image options.
00340744 In the Credits transaction logs, the externalOrderID field was not displayed at the order level. It has now been added to the Credits log.
00394916In a particular configuration’s Order Routing, orders were being assigned to Ready Backorder even when there was inventory available. This was due to inventories not being fully returned to OR because of the number of locations with inventory being more than the default inventory limit. Order Routing algorithms have been adjusted so that these orders are assigned appropriately.
00277771The Core Location API operated very slowly for requests containing a large number of locations, causing Order Routing requests to time out occasionally. A new query has been implemented to retrieve data from that table, replacing older queries in interfaces and internal logic to improve loading time and reduce time outs.
NADuring the Validate Stock step in the Fulfiller UI for an ISPU order, if there was only one item on the order and it was rejected then no Store Decline notification was sent. This has been corrected so that appropriate decline notifications are sent for these orders.
NAWhen scanning an item during fulfillment, the column for “Available Quantity” in the Validate Stock table was missing from the interface. This column now displays properly.
NAAdding gift cards to existing orders in the admin interface only provided options for CC, GX, and CyberSource. The interface has been updated so that the correct payment type options show up for a manufacturer/catalog combination.
NAThe Google Analytics of a particular client site was not working due to special characters in product names breaking the JavaScript during checkout. This has been corrected so that all Google Analytics information is recorded as appropriate.
NAWhen scanning an item barcode for fulfillment, the interface cursor defaulted to the search field. This has been changed so that the cursor defaults to the scanning field.
NADuring Ship to Store Transfer, TISPU orders became stuck in the Waiting for Transfer state if the transfer order was accepted before validating stock on the parent order. The orders could not be moved on to the Customer Pickup state. This has been fixed so that transfer pickup orders can be successfully moved through the fulfillment process
NAAs part of the ongoing performance improvements on slow APIs, the fulfillment email notification was changed so that it gets item images from the product catalog instead of the media server when possible.
NAFor a particular configuration, shipment status notifications were sending the incorrect orderType for ISPU orders during the picked and completePackage steps. The type was displayed as Ship to Home instead of ISPU. This has been fixed so that notification messages report the correct order type
NAFailed captures/credits were displayed in the V4 TLogs without any indication if the capture was successful or failed. This caused clients to not be able to reconcile accurately via the TLogs, and overstate revenue when there was a capture failure. The transaction status (success/failed) of each capture has now been added to TLogs to prevent this confusion from happening.
NAThe SAP fulfillment flow integrated in 18.1 was only configured properly for one location, so it could not be processed with other retailer locations. This has been corrected so that others can process SAP orders as necessary.
NAOrders were not properly displaying in the Fulfiller interface, as the results for multiple fulfillment states were fewer than the total amount of existing orders. All orders are now visible again.
NAAn internal script to fetch imported inventory files would exit if it found an incomplete upload, meaning that all future imports could not be completed until the incomplete file was cleaned out. This has been improved so that the script skips incomplete files and moves on to the following imports.
NAThe way that order routing queried inventory involved a number of calls that were inefficient and contributed to slow performance. These calls have been replaced and consolidated where possible, improving the speed of the routing query and reducing timeouts.
NATLogs were displaying the wrong data type for returnToStoreID as an integer, when the returnToStoreID is actually a string for the external location name. This prevented some TLogs from being validated against the schema, but the schema has now been updated to allow for returnToStoreIDs with either data type. Both integers and strings are now supported.

Previous Updates

Due to the holiday code freeze in December, the first release of 2018 combines the work done for version 17.12 with 18.1.

Features

  • Customer Search Extensions: The customer search in the CCUI now supports catalog-based restrictions. The search filters all customer results to those designated for that manufacturer account and catalog level. Additionally, the orders displayed for each customer are restricted to orders from that manufacturer.
  • Order Notes Links: It is now possible to add active links into the order notes field in the CCUI and Fulfiller UI. When the user types a URL, it will be converted to a clickable link.
  • CCUI Support for Editing Order/Item Custom Data: Custom order and item data can now be edited and saved through the Customer Care interface. Customer service representatives can now change this information when necessary.
  • CCUI Lifetime Orders by Currency: Customer support representatives can now see the total lifetime spend of a customer broken down by currency. This record now presents multiple values, one per currency type that the customer has purchased orders in before. This allow representatives to better troubleshoot customer issues.
  • Retailer Settings Override: A setting at the manufacturer account level can allow retailer overrides for fulfiller settings. If enabled, the system will use configurations specified in retailer accounts instead of manufacturer settings, in the event that multiple retailers and catalogs exist under one manufacturer group and need specific shipping configurations.
  • Cache Clearing: Caches can now be cleared with an admin tool in the OMS admin interface. This is only accessible by Kibo admins.
  • Location-Based Pricing: A new fulfiller account setting for location-based pricing can now be enabled in Core. This will be reflected when creating an order in CCUI. In the event that product pricing varies between locations, the appropriate price and location will be determined during the create order process as long as this fulfiller setting is active.
  • Return Tracking Number: Shipment APIs now support return tracking numbers so that this value can be queried and returned when it exists. This is a part of the trackingInformation data for a shipment, called returnTrackingNumber.
  • Postal Code Sort: The Location API can now filter and sort on the postalCode variable, which allows searching for a customer’s preferred location. This can be done with adding a postalCode={code} parameter to the Location API search call.
  • Manage Fraud by External ID: The Release Fraud and Cancel Fraud APIs can now accept the externalOrderID instead of the OrderID for the Kount Fraud cartridge. This enables it to act without loading up the order from Core first, which can be slow.
  • Allowed Catalogs Exposure: After making an authentication call (a POST request to /api/usermgmt/v1/authentication), a list of “allowedCatalogs” is returned as a series of integers. This data can be passed to other systems such as the CCUI. This data is only provided when allowed catalogs have been associated to that user.
  • Subtotals in Bronto: The order confirmation and shipment tracking email messages in Bronto can now display the order subtotal alongside the usual data. The email payloads include the new field $order_subtotal.
  • Custom Data on Packing Slips: Order custom data has been exposed to the packing list so that templates can display those fields when applicable.
  • Barcodes in ISPU Fulfillment: Functionality has been built within the In-Store Pickup process that allows the user to scan or enter a product barcode to verify that the correct item is being shipped. When the barcode is input, the appropriate product will be searched for on the step fulfillment interface to validate that it is on the list.
  • International UPS Shipping Labels: Shipping labels can now be created in the Fulfiller Interface for UK, DE, AT, and IT currency codes and with shipping locations in each of the respective countries. This also includes a description of the shipment.
  • Reprint/Download of Prepaid Return Shipping Labels: Customer Care Interface users can now reprint or download the prepaid return shipping label that was generated when the original shipment was fulfilled. This can be done from the returns section on the order in the CCUI.
  • Inventory Replenishment Relationships: Inventory at a location that is available for Ship to Home can now be distinguished by inventory available for replenishment to a store for Ship to Store Transfer. This includes a new API (/api/v1/routing/candidates) that returns locations available to replenish inventory to other locations, and additional work has been done with the Inventory API and Order Routing to allow this as necessary. This has been implemented primarily as support for the NG-OMS integration but could be leveraged as needed.
  • NG-OMS Preferred Location: The preferred location identifier of an order can now be passed to NG from OMS in an integration configuration, as part of the order custom data. When a new order is created in the OMS Customer Care Interface with a preferred location selected, the Create Order 2 payload includes a “preferredLocationID: {location ID}” field.
  • SAP Fulfillment Flow: Clients that process orders with a SAP system and wish to integrate it with OMS can now use a custom FSM flow. This flow supports only Ship to Home orders and includes a new state denoting that the order has been transmitted to SAP. If an order needs to be canceled, this allows the customer service representative to know whether they can cancel the order in the OMS CCUI or SAP. The new steps after the Ready state are Transmitted_to_SAP, Picking, and Fulfilled.

Bug Fixes: Customer Care

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00282964 The customer’s first and last names were not displayed in the Billing/Payment and Shipping addresses for a particular configuration. These values have now been added.
00290694 The order notes column for the time of note creation was not always being populated. All notes are now displayed in the table with the appropriate timestamp.
NAWhile adding a tracking number, the “PostNL (NL)” carrier option was not visible. Additionally, clicking on the tracking link of an existing fulfilled order with the PostNL carrier caused the user to be navigated to another URL instead of the carrier tracking site.
NAMultiple other carrier options were not visible when adding a tracking number, while an incorrect carrier was visible and selecting it would cause an error. The correct carriers are now able to be selected during this stage.
NAOrders created with the CNY (Chinese Yuan) currency format did not load. The Order Details page would attempt to load, but then throw an error message. This has been fixed so that CNY orders now load properly.
NAA number of currencies were not being formatted correctly in the CCUI, including AUD which had been missed in previous currency support work. A number of corrections have been made so that all currencies are formatted as appropriate.
NAAfter adding a payment method, interface errors caused the billing, shipping, and order notes menus to overlap each other which made it impossible to add another payment method when necessary. This has been corrected for a better user experience.
NAOnly up to 10 catalogs were visible in the “Select Catalog” drop-down menu of the Order Queue feature. This has been changed so that all available catalogs are visible.
NAThe CCUI sidebar was occasionally cut off in the screen. This menu has been changed to a scrollable section so that elements are no longer lost.
NALogging out was difficult due to the dropdown menu disappearing if the user’s mouse moved outside of a precise area. The hover area has been increased so that it is easier to navigate.
NAWhen “All Catalogs” was selected in the manufacturer/catalog option, custom data was unable to be added to a customer. An error was returned stating that the input was blank. This has been fixed so that customer custom data can be added when all catalogs are selected.
NAWhen a new customer order data value was added, the value was not immediately displayed on the custom order data tab. The cache is now cleared when data is added so that the new information is displayed immediately to reduce confusion.
NAWhen selecting the amount under “Offer Appeasement”, the currency ISO code was displayed instead of the symbol. This has been changed so that the appropriate symbol is displayed for the appeasement currency.
NAIn different views, the tax and total values of orders with the Danish Krona currency type were not being displayed. This occurred because null values were being passed in for these parameters, so a check has been added and the values display correctly.
NAThe manual assignment option did not function with any currency type except USD. This meant that an order under another currency would be unable to proceed to Ready status. This has been fixed so that orders are assigned to the correct store for non-USD currencies.
NAA number of bugs relating to watched orders were fixed. This includes that the Watched On date was not shown on the dashboard even when it was displayed on an order detail page. Also, the pagination links of Watched Orders did not progress through pages as expected. As an enhancement, a link to Watch Order was added to the sidebar under Actions.
NAAttempting to add custom data to a customer that already had custom data triggered a misleading success message. This has been edited so that the message is more uniform and holds less potential for confusion.
NACurrency support for AUD was missing from the CCUI after being enabled in Core. This support has now been added.
NAIf a user had two or more pages of customer custom data and the last page was completely filled, the “next” button would appear incorrectly. Clicking the button resulted in navigating to an empty next page. This has been cleaned up so that no blank table pages appear.
NACustomer custom data tables were supposed to indicate the current amount of data values currently being displayed in relation to the total (e.g. “1-5 of 20”), but this was not appearing. Custom data tables now provide that information.
NAWhen creating a new order with a manufacturer and catalog already specified in the title bar, the manufacturer catalog selector was not automatically populating with those values. These fields now auto-populate as intended.
NAWhen there was only one customer custom data entry left for a customer and that entry was deleted, a null pointer exception occurred and replaced the table. Checks for null custom data have been added and the table now updates cleanly.
NAWhen a user with "allowedCatalog" parameters selected "All catalogs" from the manufacturer/catalog dropdown, the order queue counter displayed the count of all orders within the "manufacturerID" parameters, even when all proper orders were listed. This was fixed so that order queue counts remain accurate under allowedCatalog.

 Bug Fixes: Core Order Management

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00340877 The firstName and lastName values for a particular configuration’s logs and packing slips were being pulled from billing information instead of shipping. These properties are now filled from the proper shipping data.
00312465 A particular configuration’s custom report was showing incorrect data by displaying a WebCustNbr parameter in place of LoyaltyID (WME ID). This has been resolved so that the parameters are accurate.
00340939 A particular configuration’s transaction logs were showing a different value for the shipment level fulfillerTotal and the item level fulfillerTotal. The calculations have been fixed so that both fulfillerTotal parameters now match.
00369276Returns could not be created from the customer account space if the interface was in French or Canadian French. This error has been fixed and French-speaking customers can now create returns.
See ResolutionThe language of the fulfiller interface suddenly shifted to the order’s language (if different from the interface language) when viewing pages that contain orders. The system sometimes ignored attempts to switch the language back by adding a language_id to the query string. This has been corrected so that the chosen language for the interface user is maintained. Support tickets include 00310517, 00309526, 00328874, 00360693, 00367858, and 00308721.
NAThe Get Order and Create Order schemas did not list the isBilling and isShipping parameters and their definitions. The schemas have now been updated.
NAAlthough test orders are never assigned, the system still made a regular call to OrderRouting to try to assign them. The release_wfma_orders cron has now been altered to exclude test orders on production environments from being automatically released. This relieves load on order routing.
NADisabled admin users were still able to access the user management APIs. A check has been added so that disabled users are not able to access functionality.
NACustom attributes for networks were not returned in GET calls to the Location API, even after being added successfully. Custom data has now been added to the response body so that the information can be retrieved when needed.
NAThe search retailer widget only worked the first time each page was reloaded. Suggestions did not always appear properly when search strings were entered and then deleted by backspace. This has been fixed so that suggestions appear live whenever characters are entered into the text field.
NAThe Assigned Orders table in the Fulfiller Interface did not clearly distinguish between ISPU and TISPU orders, and needed some backend work to make it more easily editable. The table has been updated to include these improvements.
NAThe order page failed to display due to an unknown timezone exception triggered by New Zealand orders whose timezone was being referenced based on currency. This has been changed so that the New Zealand currency and timezone do not return errors and the order can load.
NADecision Manager was unable to update orders while checking fraud when the External Order ID did not match the CS Merchant Reference Code, which were used to communicate between OMS and Cybersource. The Cybersource cartridge has been updated with multiple checks so that the order does not become stuck in Payment Authorization.
NADuring the Validate Stock Step in the fulfiller interface, rejecting a line item appeared to cause an error. However, refreshing the page would reveal that the rejection processed properly. Interface improvements have been made so that the page immediately updates.
NAWhen a new order is created with an address that was already used in another order under a different email or customer ID, an "address matches existing customer" message and link appears. This link usually led to a page with an empty table where it was supposed to show matching customers, but sometimes listed customers that did not actually match the address. The table references have been updated so that this table displays the appropriate customers.
NAWhile creating locations in the Location API, an error would be thrown if Shopatron-User-ID was not passed in the header. Additionally, specifying a locationID would return an error for duplicate locationIDs. This has been fixed so that locations can successfully be created through API in these cases.
NAWhen re-printing a shipping label through the Fulfiller UI, all return shipping labels were identical regardless of corresponding shipping label inputs. This has been fixed by updating the tracking number reference, as well as defaulting the weights of return labels to 1 pound.
NAOnBlocks stores that were redirected to https displayed non-secure image content warnings for images that still used http source URLs. A script has been written that replaces applicable image URLs with secure https versions.
NAShip to Store transfer shipments were not following the proper transfer routes set up in order routing. This has been corrected so that the appropriate order routing rules are now enabled for transfer shipments.

API Documentation

Progress on online API documentation is continuing. In the past couple of months, a number of new guides have been added and existing ones have been enhanced. Upcoming guides include Inventory, Customer, and XML-RPC APIs, as well as some functional improvements.

Features

  • Chrome Security Updates: This year, Chrome browsers began implementing changes to alerts regarding the security and connection settings of pages. With the October update of Chrome, security alerts were expected to be displayed on HTTP pages of Kibo client stores with password or credit card fields. To handle this, stores and sites hosted on OMS Core and Kibo-hosted custom sites will default to HTTPS throughout and should not have security errors if the client has an approved SSL certification for the domain.
  • Location Management (Phase 1): Locations can now be better managed through APIs to add, edit, and delete location networks and attributes, including custom attributes. These can be accessed through endpoints such as /api/system/v1/location/ and /api/system/v1/network/ for the appropriate elements in and out of networks. See Kibo Project Team for more instructions and request samples.
  • External Customer Data: A new ManufacturerConfig field in the ManufacturerConfig API, called externalCustomerDataSource, has been added. This indicates whether an external source should be used for customer data or not and can be toggled in the Fulfiller Account Settings user interface.
  • Ship to Store Transfer Messaging: Email messaging has been added to enhance Ship to Store Transfer functionality, so that customers will be informed if they cannot pick up their order immediately. When the store does not have stock, a notification email explains that the order is being transferred to the store. When a replacement transfer is made due to a damaged or incorrect transfer item, a similar email notifies the customer of the transfer in progress.
  • Alliance Data Systems Payment: Payment with Alliance Data Systems (ADS) credit cards has been added to Create Order 2 as an authorized payment type. Any new manufacturer wanting to use ADS in Create Order 2 needs to make sure the “gateway_configuration” value in the database has the column “use_co2” set to true.
  • Vantiv URL Override: Kibo OMS previously did not support custom URLs for Vantiv implementations. This made certification difficult for some clients who needed to do testing with Vantiv eProtect. OMS now has the ability to override the default URL on a manufacturer or catalog basis for Vantiv gateways. If override information is present, then it will be used in place of the default. This information is provided in an overrideParameters element when calling /api/v2/payment/action/registerEProtectPayment, as in the example below. The manufacturer gateway has the URL set to “https://request.eprotect.vantivcnp.com/eProtect/paypage”.
    {
      "manufacturerID":00000,
      "catalogID":1,
      "currency":"USD",
      "paymentType":"LV",
      "cardIssuer":"DC",
      "cardNumber":"<credit-card>",
      "cardSecurityCode":"<cvv>",
      "overrideParameters":{
        "payPageID":"SDkj23LKdn1JRL",
        "merchantID":"1111111"
      }
    }
  • Delete Inventory API: There is now an additional inventory API that can delete inventory products based on a specified locationID and partNumber, UPC, or SKU for a given fulfiller. The new API endpoint can be called using an HTTP DELETE request and the endpoint /api/v5/inventory/delete?fulfillerID=<ID>, such as in the below example.
    {
        "items": [
            {
                "locationIDs": [000000, 111111],
                "itemIdentifier": {
                    "partNumber": "InventoryItemA",
                    "upc": "InventoryItemA",
                    "sku": "InventoryItemA"
                }
            }
        ]
    }

Bug Fixes: Customer Care

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00278699Splitting orders in the CCUI with manual assignment was not allowing splits to be done by quantity, only showing 0 or the total as the quantity options. Now, orders can be split by any quantity up to the total.
00293004When selecting a location for manual order assignment, the order was being automatically assigned instead. This has been fixed so that the correct location ID is taken from the page.
00249816When selecting "Nova Scotia" in the territories field, the abbreviation would automatically be set to "NT" for Northern Territories. This abbreviation has been updated to become "NS".
NATo combat CCUI slowness, a number of tweaks have been implemented. This includes caching in the order queues page, fixing parameter ambiguity errors, and decreasing the amount of API calls made behind the scenes.
NAIn the "Ready/Backorder" order queue page, users were not able to update the values of "Price Paid", "Unit Tax", or "Quantity" fields as expected even though a validation message was generated. This was caused by a loop error and has been corrected.

 Bug Fixes: Core Order Management

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00279071Some dealers with special characters in their username were unable to sign up and log in with the generated password that they received, due to special characters. Usernames are now restricted to alphanumeric characters, so dealers will see an alert if they attempt to use special characters.
00246808Gift card recipient emails had a field for an image of the card type, but this field was never populated. Images have now been mapped to gift card sources, so they will be displayed in these emails.
00277771Tron received a new OAuth token every time it made a call to order routing, which was unnecessary and caused additional requests to the OAuth server that could be skipped. OAuth tokens have now been cached to simplify this process.
00296047Support for European locales and default currencies have been added to the Create Order API, following failures in Belgian catalog orders that caused errors due to their locale/currency combination.
00289873A particular client’s Ready Order Download, customer comments, and some gift order details were not working as CDATA due to incorrect coding of special characters after the move to PHP 5.6. This has been corrected and the relevant manufacturer added to the CDATA list.
00296421A particular client’s input file required a new endpoint and upload folder to be created. This has been taken care of so that the relevant file is uploaded to the correct directory.
00277771Slowness in order routing sometimes caused orders to fail. As part of ongoing improvements on this issue, a certain slow query has been optimized.
NASome order routing filter comparisons were failing due to data type mismatches, meaning that certain ready orders were assigned to locations when they should have been canceled per the filter criteria. The comparison logic has been updated to correct this.
NAAn edge case for a client’s custom reporting held the potential for causing exception errors if there were no orders placed that day. This has been handled so that the report will display no content instead of errors.
NAThe maximum string length for creating bins in the Pick & Pack menu was not being respected, allowing for the creation of bins with too-long names. This has been corrected so that a pop-alert is generated and prevents creation instead.
NASearching for manufacturer catalogs and specifying 200 results per page displayed only 100 results. The allow perPage size for this Get Catalogs call has been upped to account for this request.
NAIn particular clients’ fulfiller interface, the displayed audit status was not updated upon cancellation of the audit and a manual refresh of the page was required to reflect this change. This has been corrected so that the displayed status updates without a refresh.
NAThe “Create Shipping Manifests” link in the fulfiller interface did not make sense to be displayed under certain scenarios, such as when using Canada Post and CARS. Additional logic has been added so that this link only displays when necessary.
NAWhen a particular client placed orders using Ship to Store Transfer or In Store Pick Up, the retailer was unable to advance through fulfillment from the stock page due to a logic error that affected the displayed options for the order. This has been fixed for both types of orders.
NACanadian tax overrides were being displayed in the admin interface for bundled clients, under “Edit Shipment > Change Shippers”. As these should only be displayed for unbundled clients, logic has been added to disable the override tax in the case of order creation if the client is bundled.
NAIf a manufacturer’s catalog had the catalog_type 4 (SIMPLY_COEX), customers created for all other catalogs through Create Order 2 were given the manufacturer prefix. This has been corrected so that customers only show the manufacturer prefix when applicable.
NAOrder assignment occasionally caused deallocation of unrelated items after the assignment and rejection of shipments, due to old shipment IDs being preserved as arguments. The logic now discards these old IDs so that only the relevant items are deallocated in inventory.
NAOMS fees were not being calculated properly for credit card payments, because weighted percentages were set incorrectly upon order creation. This has been fixed so that these percentages and fees are properly calculated based on the card issuer.

Patch Fixes

As 17.11 is the last major release before the holiday season, there have been more issues addressed in patch than usual. The most significant issues released in patches after November 14th have been noted here.

Support TicketResolution
00277771There have been more Order Routing optimizations to reduce slowness. This includes enhancing a particular query, removing duplicate calls, and shortening timeouts.
00321715After editing the ISPU location of an order, the location data was deleted and the store set to inactive when it should not have been. This has been corrected.
00314391Due to conflicts caused by a double click, In Store Pick Up orders in a particular configuration were stuck between the acknowledgment and Print Pick Sheet stages. Protections against this have been implemented for the future.
00305849 & 00306879In Store Pick Up orders were being moved to the stock validation stage after an order item was canceled, when they should have remained in Waiting for Transfer. This has been fixed so that orders stay in the proper status.
00252731 & 00303450Orders of a particular configuration that had some of their items canceled became stuck in payment hold, as their fraud restriction was unable to be removed. This has been corrected so that fraud can be removed and the order released from hold.
NARemoving fraud after cancelling part of a shipment caused both items to be moved into Ready status, rather than one item in Ready and one in Cancelled.
NAIn CCUI, the charge failure order queue count and order cards did not match up when a catalog was specified as it appeared to be pulling a cached version of the charge failure of all catalogs. This has been fixed so that the queue and cards match for the proper catalog.
NAAt client request, the checkboxes in the In Store Pick Up menu of the Fulfiller UI have been moved to be more user friendly.

Features

  • Default Shipping Carrier: Merchants and fulfillment partners can now set a default shipping carrier in the OMS Admin view. In addition, the default shipping carrier will be at the top of the carrier list on the ‘Enter Tracking Info’ screen. When the user is entering shipment data, this default carrier is pre-selected. This will save time and cut down on user error.
  • Product Details Hyperlink: A hyperlink to an external details page can now be added to product names that will be displayed in the Customer Care and Fulfiller interfaces. This optional productDetailsURL field has been added to the Create Order API call for the page URL to be passed in, as part of Order Item > Product objects.
  • New Currency Support: Non-commerce currency support for a number of new countries has been added. Orders can now be placed in the following additional currencies: HKD, JPY, MXN, RUB, SGD, KRW, CNY, DKK, PLN, RON, ARS, BRL, HRK, CZK, UAH, HUF, INR, IDR, IRR, KWD, TWD, QAR, SAR, THB, AED.
  • Order Type in Notifications: The order type property (STANDARD, ISPU, TRANSFER, etc.) has been added to order notifications so that clients can distinguish the difference between different order type notifications.
  • Search by Shipment ID: The Shipment ID parameter has been added as a search option to the Order Search and Quick Search in the Customer Care interface, alongside the Order ID.
  • Exposed Capture Function: A Capture Payment API has been created so that funds can be captured on request. This should only be used by manufacturers who are decoupled and will use the external payment configuration. This capture will be at the order level and can only be performed on orders that are in Ready or Fulfilled statuses. An example of when this might be used is if an In-Store-Pick-Up order is not in stock and the distribution center ships the product to the store. The client could capture the funds here since the order is already en route.
  • Edit Users as Admin: Manufacturer administrators can use the User Management API to reset a user’s password and edit other information. Previously, only Kibo administrators could do these actions. Calls to this API use the endpoint https://{{core-url}}/api/usermgmt/v1/user/{{userID}}with the information to be changed in the body.
  • Pick Process Configuration: A new configuration has been added to specify the final/exit state of the pick process, based on the client’s workflow. Previously, when the pick process was complete then the items would always be automatically pushed into the first step of FSM. Now, when items are picked they can be moved directly into the specified state to bypass the initial acceptance step when necessary. Catalog configurations have been created for each state (e.g. FSM_SKIP_TO_STATE_ISPU). In Store Pick Up orders can be configured with “FSM_CLOSE_PICK_WAVE_EXIT_STATE_CODE_ISPU” set to a numeric state code.
  • Register Payment API: A new API has been created to implement eProtect paypage registration. This API allows for the use of Vantiv eProtect to register payment data and return registration IDs. The POST request is made using the endpoint /api/v2/payment/action/registerEProtectPayment.The body contains the card information:
    {
      "manufacturerID":00000,
      "catalogID":0,
      "currency":"USD",
      "paymentType":"LV",
      "cardIssuer":"VI",
      "cardNumber":"0000000000000000",
      "cardSecurityCode":"000"
    }

Bug Fixes: Customer Care

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
NACustomer Service Representatives were experiencing long delays and the inability to load retailer accounts and retailer lookup pages in the OMS front end. This functionality has been enhanced so that results should be loaded quickly on multiple browsers.
NAThe date and time were not displaying application-wide across the Customer Care interface, and there was a discrepancy between browsers regarding whether both date and time were listed for returns. This has been corrected so that the appropriate information is displayed across the application.
NAThe Customer Care interface has been updated to follow dependency rules established by the 17.9 feature "Product Dependencies". Item displays now show the product associations, cancelling a parent item in CCUI now cancels the child items, and items with dependencies are not split by quantity.

 Bug Fixes: Core Order Management

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00252297Some locations were being stored incorrectly in the Inventory Location cache. To manage this, a page has been added to the COEX interface with an option to clear that cache entry on request. This page includes a search form with fields to select the location code. Location results from this search can then be deleted from the cache.
00271793Report delivery has been moved to a S3 server to improve reliability over sending them through SFTP. A new interface under Reports has been built for clients to retrieve their custom reports from S3 on demand. Clients who need to continue using FTP servers can still access their reports through an additional script that syncs files between S3 and SFTP.
00294580For a number of clients’ manufacturer sites, the external store numbers on the Waiting For Manufacturer Acceptance and Backorder screens were being displayed as Kibo store numbers. This has been changed to display the appropriate external store number.
00257283Dealers whose primary location has shippable set to “no” in the shippable location table could not update In-Store-Pick-Up locations successfully, as all info was wiped on save. Corrections have been made so that these locations can be edited.
00237067Some site elements on the manufacturer and retailer Reports page were misaligned, hiding buttons and obstructing functionality in some browsers. These elements are now aligned properly.
See ResolutionBundled clients received notification emails for failed charges, when they should not receive them due to Kibo managing the payment processing. These emails will now only go to unbundled clients. Tickets raised for this issue were: 00297404, 00297409, 00297413, 00297415, 00297417, 00297421, 00297481, and 00297959.
NAIn Ship to Store Transfer, when a transfer order was rejected then that store was considered unfillable for the item. This means that any new transfer orders sent to the store for that item would automatically go into Customer Care. Now, a new transfer order is automatically created when a shipment is rejected which prevents that store being permanently marked unfillable.
NAOrders received from Swedish Krona catalogues were needlessly being flagged for fraud review due to their perceived high value, as the total value of the order was being recognized as USD instead of SEK. Now, the total is converted to USD before being sent to fraud so that these flags will not occur.
NAA particular client’s InventoryOrderAssignedFulfiller notification emails were not being queued in Bronto when an order was reassigned, because the code to send emails was not being triggered after reassignment. This has been fixed so that emails will be sent to the queue automatically.
NAIn the Create Order Authorize call, a configuration for PAYMENT_TYPE_ALLOWED_SHOPATRON_TOKEN was not required to be enabled, but the next step of Create Order required it. Thus, Create Order Authorize now checks that this value is enabled first.
NAWhen a certified order was cancelled and uncancelled, it was put into "Available Certified" status when it should be in regular "Available". This was due to legacy code that has now been updated so that uncancelled certified orders go into the proper status.
NAClients that do not use security codes on their gift cards were encountering errors with ValueLink payments, as OMS expected a code and could not capture the card. This has been changed so that a security code is not necessary with ValueLink cards.
NAIn Store Pick Up orders that were fulfilled via API call were still listed with READY status. This did not affect orders fulfilled through the user interface. These orders are now moved to the fulfilled state.
NAA client was not receiving warning messages when uploading a bin inventory file with a significantly large quantity change. This warning message now generates before confirming the file import.

Patch Fixes

The following list summarizes some post-release enhancements and resolved issues.

Support TicketResolution
NAA configuration’s reports were not uploading to the new S3 server. This was identified as being due to file path and segmentation faults, so it has been corrected and all relevant reports should now upload to S3.

Features

  • Enhanced Location Import: To streamline the process of uploading retailer and manufacturer locations in bulk, the Admin UI now has improved import processes that accept CSV files. The existing XML uploader has been updated to be more effective and flexible in how it processes the new data.
  • Branded Credit Cards: Clients can now identify when their private branded credit card is used so that they can award additional reward card points to the customer. When a payment is processed through CyberSource, the sales Transaction Log passes the information to the client who can recognize a branded credit card by the first six digits and then credit the consumer’s account with the appropriate amount of reward points.
  • Editing Custom Order Data: As requested by multiple clients, custom order and item data can now be edited via APIs after order creation. When an order is created and sent to Kibo OMS with custom order data fields, the data may need to be modified after creation. That modification is now possible with GET, POST, PUT, and DELETE API functions at the endpoint order/{orderID}/customData/{customDataID}.
  • Product Dependencies: Services, such as gift wrapping, can now be tied to products and displayed in the Customer Care interface. These services can be captured by OMS either immediately when the order is placed or when the item is fulfilled. This will improve customer support through managing these products and associated services, such as refunding the service if needed. This functionality will be a configuration on the client payment plan.
  • Customer Custom Data: The Customer API now allows for the creation and modification of custom data for individual customers. The Create Order API also accepts customer custom data as acceptable input during order creation. To view a customer’s custom data, use the standard Customer GET method with the unique customer ID. The custom data will be included in the response. The below example creates a new customer with custom data via an HTTP POST request and the endpoint: /api/v2/customer/.
    {  
       "firstName":"John",
       "lastName":"Smith",
       "email":"qa12341234123412r4@shopatron.com",
       "phone1":"555-555-5556",
       "password":"Quality01",
       "customData":[  
          {
             "name":"Non-MFG/CATALOG",
             "value":"TESTING"
         },
          {  
             "manufacturerID":"3456",
             "catalogID":"1",
             "name":"Custom Value 3456.1",
             "value":"Value 1"
          },
          {  
             "manufacturerID":"3456",
             "name":"Custom value 3456",
             "value":"Value 1"
          },
          {  
             "manufacturerID":"15569",
             "name":"Custom value 15569",
             "value":"Value 1"
          }
    ]
    }

Bug Fixes: Customer Care

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00231066Gateway time out errors in a particular configuration were forcing orders into Customer Care. The frequency of these time outs should now occur less frequently.
NAOn the Customer Care order details page of an order with a transfer, the order items were all listed for each shipment due to the items not being organized by shipment ID when displayed. They are now organized so that only the items belonging to a given shipment are displayed on the card.

Bug Fixes: Core Order Management

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00284807A couple of configurations’ orders were not being checked for fraud after recent changes, as the configuration was referencing the wrong default fraud option.
00286868Order resolve stopped working whenever it encountered a particular SQL failure. Protection has been added to handle these failures so that the resolve process remains functional.
00277146Orders released from the CyberSource Decision Manager of a particular configuration were not being released from Payment Hold at the same time. This functionality has now been implemented.
00136411When a preorder was placed, no inventory was decremented which could lead to overselling. Now, preorders are tracked relative to inventory and allocate inventory accordingly.
NAThe filters on the Late Orders page of the Fulfiller UI were being ignored, resulting in incorrect sorting and some slow load times. These filters now properly categorize orders.
NAWhen using a configuration in IE 11 and Chrome 56.0.2924, clicking “ready for pickup” while validating inventory for an in-store pickup returned the user to the top of the page with no record of the process in the logs. The button now properly updates the pickup order status.
NADuplicate line items caused incorrect ISPU order assignment for a particular configuration. The Inventory tools now consolidate duplicate items and thus assign orders properly.
NAA configuration’s inventory import process was not properly mapping part numbers when the uploaded file was in CSV format. This prevented any inventory from being queried in the Fulfiller UI. Mapping is now successful and the correct data can be accessed.
NAThe Inventory Refresh page of the application recently began displaying MySQL errors instead of inventory data. This has been fixed so that the page works as expected.
NAThe External Item ID parameter was not included in the GET response of the Order Item API. It has now been added to the response.
NAThe setting “Send Customer Pickup Reminder” for in-store pick up orders was integrated with the pickup deadline in a way that was not ideal. The function has been improved, and customers will receive daily pickup reminders until the order is either canceled or picked up.
NAA particular configuration’s gift cards were not being charged before credit cards or other payment gateways. They have now been set as the priority so that they are always charged first.

Features

  • Ship to Store Transfer (Phase 2): This phase of Ship to Store Transfer will expand the functionality of Ship to Store by enabling clients to transfer inventory from one location to another within the Kibo system utilizing Kibo’s Order Routing capabilities, Fulfiller Interface and Fulfiller messaging. Clients will now be able to transfer inventory from one store to another to facilitate an in-store pick up order. This transfer of inventory will be synchronized to consumer messaging and integrated into the existing Fulfiller Interface. Additionally, the capabilities of Order Routing have been improved to effectively select where the inventory can best be sourced from.

Bug Fixes: Customer Care

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00262954The Customer Care interface would timeout when trying to display an order’s items if there were a large number of items (in this case, over 40). Now the list of order items loads much more quickly and displays correctly.
NAWhen viewing the Available/Requested Inventory on the order queues page, sometimes it would be difficult to see the information due to how it was loaded and displayed. Interface improvements have been made.
NATrying to view Charge Failure or Refund Failure order queues as an Admin resulted in a Page Not Found error. This has now been corrected to display the appropriate queue.

Bug Fixes: Core Order Management

The following list summarizes enhancements and resolved issues for this release.

Support TicketResolution
00254577In a particular configuration of PayPal, the “refund” button remained clickable even after the refund was processed. Clicking the button repeatedly sent multiple refunded payments to the customer. This has been fixed by a previous patch.
00263924In a particular configuration, using the Search Returns API with a parameter to specify how many results should appear on each page caused a 500 Internal Server Error. This has been fixed to allow for pagination.
00266729When orders were placed with multiple order items for the same product, a bug in the logic of the script summed up the deltas on product IDs. This resulted in the appearance of over-allocation in inventory, ultimately causing negative allocates.
00276825A few configurations experienced empty packages with payment totals being included in some orders. The automatic order resolution process was picking up inventory orders when it did not need to, creating these empty packages.
NASome configurations were experiencing high amounts of order routing failures due to some filters being marked NULL, which caused errors. Now any NULL filters are automatically changed to DIMENSIONLESS which is an acceptable type.
NATables in the PayPal payment gateway configuration were out of date or incorrect, preventing the processing of refunds. The PayPal tables were updated in all environments.
NAThe billing name for payments was sometimes not displayed in the Admin view of a particular configuration even while it was displayed in Cybersource. This resulted in failed Cybersource captures but has now been corrected by removing redundancies in how billing information is provided.
NAGetting inventory information failed if a postal code that was provided could not be resolved to a latitude/longitude. It was possible for codes to not be resolved due to invalid postal codes, a mismatched country code, or a lack of records in other APIs such as Google Geocode. Now all inventory results are returned with at least a best guess for the distance value instead of failing.
NATransaction Logs were experiencing fatal errors after a recent release, caused by an undefined method that has now been corrected.
NANew clients’ default set-up for Transaction Logs did not include the collection, transform, or transport values. This prevented the logs from generating. New default values have now been set.
NAWhen a consumer order had an associated transfer, the order logs displayed $order_link instead of a text link to access the transfer. This was caused by an extra space in parameter values and now appears correctly.
NAA particular configuration’s user search function only returned results with manufacturer associations. Now the search also returns results with retailer associations.
NAShipping refund amounts were displaying incorrectly in the Return summary for some EU orders. The logic has been changed to correctly reflect the amount.
NAThe "Available On" date in backorder emails was in the US date format when sent from EU merchants, causing confusion and unnecessary cancellations of items put into backorder. The format has now been updated to support EU formatting.

Features

  • Multi-Catalog Cybersource: Catalog-specific and multi-catalog support is now available in the Cybersource Fraud Cartridge.
  • Transfer Order Logs: The Customer Care interface now displays transfer order logs in the transfer order and the related consumer order.
  • Custom Order Routing: Orders can now be routed based off of custom item data and product identifiers by adding new filters.
  • Custom Return Locations: Users can now specify a return location that’s different from the stored return location.
  • Returned Product IDs: Product number, SKU, and UPC can now be displayed when creating and managing returns.
  • Get Return Location: The return location can now be retrieved in Customer Care.

Bug Fixes

The following list summarizes enhancements and resolved issues for this release:

Support TicketResolution
00142875Order queues were not displaying in Customer Care due to an error when transfer orders were present.
NAThe Order Watch table was labeled with the incorrect date, and other interface improvements were made.
NASome orders with both credit card and Clutch payments were not queuing confirmation emails properly.
NASome transfer order shipping labels had incorrect contact info.
00165321Some late orders were not displaying in the Fulfiller interface.
NAAn error message was displayed when searching by SKU or UPC in the Fulfiller interface.
NAManually creating a TLog failed repeatedly for some clients.
NAA particular inventory client’s orders were not converting to In Store Pick Up orders..
NAGift card registration dates did not take Daylight Savings into account.
00221719The tracking link for shipments via Canada Post were improperly linking back to the Customer Care Interface.
00189408 & 00234056Decline notifications did not include a reason code for some clients.
00237921Sales reports were not generating for certain clients.

Features

  • Vat tax is now included in the Refund Price on return emails.
  • Added Tax-From and Shippable toggle to the view Manufacturer and View Retailer admin screens.
  • Enabled the ability from within the account to specify where returns need to go.
  • Created packing list variables to display Customer’s Company Name and Tax ID.
  • Improved the logging of transactional logs by saving more ifnormation and adding to S3 in order to make them available in fulfiller_account-settings.
  • Added more checks/validation to our transactional logs to prevent missing orders in the future.
  • Added PostNL to the list of OMS carriers supported.
  • Added “Department” to dropdown option for Product identifier for Pickwaves.
  • External Order ID is now able to be displayed in the Fulfiller UI rather than just the Kibo Order ID.
  • Added a catalog config in order to enable functionality that allows returns to physical gift cards.
  • refundType has been added to the output parameters for the Return API.

Bug Fixes

The following list summarizes enhancements and resolved issues for this release:

Support TicketResolution
N/ACanada Post sometimes would respond with error on shipment cancel.
N/ATransfer In Store Pick Up orders failed to create when transfer creation failed.
0021317Pick waves were not populating in English for some clients.
N/ACanadian Tax Overrides were being displayed in Admin interface and CCUI for bundled clients.
N/AProduct availability “D” (Discontinued) was being ignored by CO2.
N/AVAT Taxes were being applied inconsistently
00189408Some clients were not receiving Reason Codes or Reason Descriptions in some store decline notifications.
00238775Guam was incorrectly being treated as a country separate from the United States.
00159119Single item discounts were not working for some Pro Store clients.
N/AEuropean dealers were not receiving an “assigned orders” notification when a Ship to Store or Shoppers Choice order had been placed.
00236800Failures were seen when trying to create/print Canada Post labels.
N/AAdded integration to Postcodes.io to get missing UK Postal Code information.
N/AReturn locations were not working for international return addresses.
N/AWhen clicking the auto-assign button on the Waiting For Manufacturer Acceptance order queue when there was not an existing valid location with inventory available, a success banner was appear even though the order remained in WFMA and was not assigned.
N/ACharge and Refund failure order queues were missing from the navigation in Customer Care UI.
N/ASearching for product in Customer Care was not working with accounts with multiple catalogs.

Features

  • Added a New Reason Code within CCUI— “No Inventory” is now a valid cancellation reason within the CCUI
  • Display of Customer’s Shipping Company Name and Tax ID— On Order View, we now display the customer’s shipping company name and tax ID in CCUI and order view for retailer and manufacturing accounts.
  • Canadian Tax Overrides—The system now supports tax overrides for our Canadian clients.
  • Reference ID in downloadable statement—A column has been added to downloadable statements to show Reference ID.
  • Dealer Participation in Denmark and Lithuania—Participation of dealers in Denmark and Lithuania has been enabled.

Bug Fixes

The following list summarizes enhancements and resolved issues for this release:

Support TicketResolution
N/AOrders on the waiting for manufacturer acceptance order queue page could not be auto assigned.
N/AThe user API call has been removed from customer care order notes and instead will just populate the name returned with the order note call.
00133212Some orders, notifications were seeing an error when transitioning from step code 100 to 200 due to a UTF-8 encoding problem.
00138640EUR currency was not allowing the English language because the locale field was used to determine both the language and currency of the order. A new locale (currencyLocale) has been added
00159119Single item discounts were not working for certain Pro Store clients.
N/AJava error when trying to view expected delivery date in the fulfiller interface.
N/AIncorrect statement displayed under the shipment details header on the Admin interface after removing the existing tracking number of a “Ready” order.
N/ACurrency symbol was unnecessarily displayed in exported Customer Orders reports in XLS format.
00172063Consumers were unable to purchase gift cards using PayPal as their payment method from some clients.
N/AMerchandise credits were not processing for some orders.
00171566Promotional code discounts could not be removed when the items were removed from the shopping cart.
N/AStore decline notifications did not work for line item edits.
N/AThe Kibo OMS “Help” tab was directing users to Kibo Community “Login” page.
00246811The returns API calls were failing to process for some clients’ point of sale systems.

Features

  • Improved Group Creation Workflow—The group creation workflow now has fewer required steps. Some of the changes include:
    • The Request Logic section only displays when Use inventory is selected.
    • The fulfillment limits only display when a route is selected. Otherwise, Standard Ship to Home is selected by default.
    • All groups display in the menu for adding locations to a group.
  • Canadian Postal Code Update—The internal databases now reflect all necessary Canadian postal codes.
  • Order Deallocation Limit—You can now configure a deallocation limit under Order Routing to limit the number of times a single order can be assigned, rejected, or re-routed.
  • Search Locations in Order Routing—You can now search the Order Routing table based on the following criteria:
    • Location Name
    • Address
    • Location ID
    • External ID
  • New Route Story UI—The UI for the route story is now updated based on usability testing. You can now leverage the context of the whole route, including other groups, to choose after actions when creating or editing a group. Similarly, the Edit, Copy, and Delete group functionality is now removed based on feedback. All other functionality remains the same.
  • New Locations Page—The Locations page is now updated.
  • Password API—You can now use the API to manage the password for internal employee accounts. The new operations are:
    GET /api/usermgmt/v1/user/{userID}/location/
    POST /api/usermgmt/v1/user/{userID}/location/
    DELETE /api/usermgmt/v1/user/{userID}/location/{locationID}
  • New Pick Up Request API—You can now leverage the notifyPickup API to automatically trigger a Pick Up Request after completing the Prepare for Shipment step in the Fulfiller UI.
  • New Packing List Variables—You can now leverage company_name and tax_id packing list variables for the customer’s shipping address .

Bug Fixes

The following list summarizes enhancements and resolved issues for this release:

Support TicketResolution
00211865Fixes an issue that prevented transfer orders from leveraging correct catalog settings.
00206427 & 00210420 & 00204910Fixes an issue that prevented the application of electronic gift cards to an order.
N/AFixes an issue that prevented capturing and displaying MaxMind data successfully for some orders.
N/AFixes an issue that prevented manufacturers from exporting single inventory configurations. Now you can export a single inventory configuration to all FTP locations for that configuration using the export_id parameter. To send the configuration to only one FTP location, you can use the export_id and ftp_id parameters in conjunction.
00192609Fixes an issue that prevented the Checkout page from displaying the promotion codes applied to the order.
00144387Fixes timeout issues between Kount and Kibo.
00179864 & 00240194Fixes an issue that prevented monthly fees from being charged to a credit card.
N/AFixes an issue that caused French language pages to display incorrectly, with incorrect translation, characters, and non-functioning buttons.
N/AFixes an issue that prevented refunding the shipping tax on an order.
00161855 & 00136849 & 00147722Fixes an issue that caused incorrect store hours to display in emails sent to customers.
N/AFixes an issue that prevented certain manufacturers from displaying in the Order Routing search bar.
Angela FausoneRelease Notes – OMS