June 4th & 6th 2024, Release Note: Adaco: Improvements to Barcode Management, Prompt to Route Requisitions for Approval, Vendor Names in Mobile Punchout Requisitions

Summary

“Great Idea! Two of these features were originally raised as Ideas in our Customer Community. The suggestions helped our teams to design and release enhancements which are now available to everyone.

Look for the  symbol to see which feature started life as an Idea!
Why not share your inspirational ideas (or vote on someone else’s) today!

Select the release feature from the table below to be taken directly to that section of the release note.

Release date for all features: June 4th (EMEA & APAC) and 6th (US) 2024

Improvements to Barcode Management

• Enabled by default? - Yes
• Set up by customer admin? - No
• Enable via support ticket? - No
• Affects configuration or data? - No

What's Changing?

Product barcodes can now be accessed when right-clicking a product on the main Products page/search results. Also, when attempting to enter a duplicate barcode for a product, the system will now display the already assigned product code.

Reason for the Change

To speed up the general process of managing product barcodes.

Customers Affected

Customers who use barcodes to identify their products and recipes

Release Note Info/Steps

• On the main Product page, right-click a product and select Barcodes

Fig.1 - New option to access barcodes from the product search page

The system does not allow duplicate barcodes to be entered. When attempting to do so, the item (can be a product or recipe) it is already assigned to will display in a warning prompt. See Fig.2.

Fig.2 - Seeing where a barcode is already assigned

Prompt to Route Requisitions for Approval

• Enabled by default? - Yes
• Set up by customer admin? - No
• Enable via support ticket? - No
• Affects configuration or data? - No

What's Changing?

Users will now be prompted to route their requisitions for approval (when approval is required).

Reason for the Change

To avoid users forgetting to route requisitions for approval.

Customers Affected

Customers who implement an approval process on purchase or outlet requisitions.

Release Note Info/Steps

When a user clicks on Save when creating or amending a requisition they will be prompted to route the requisition for approval, as shown in Fig.3.

Fig.3 - Prompt to route a purchase requisition for approval

When the user selects Yes, the approval screen will open from where they can route the requisition appropriately. 

Where the Outlet has a default approval route set (Property Setup > Outlet > Enable Mobile Ordering Default Route), that route will be automatically selected in the Route List drop-down. See Fig.4.

Fig.4 - Default route automatically selected when opening the approvals form

A requisition will require approval when either:

• It is a purchase requisition which contains at least one product that requires approval
• It is a purchase requisition which is derived from a punchout interface that requires approval
• It is an outlet requisition and the option Administration > Property Preference > Requisition > Approval Needed for Outlet Requisitions is ticked

In all of the above cases, the user will be prompted to route the requisition for approval when clicking on Save, except where the requisition has already been routed for approval.

Vendor Names in Mobile Punchout Requisitions

• Enabled by default? - Yes
• Set up by customer admin? - No
• Enable via support ticket? - No
• Affects configuration or data? - No

What's Changing?

The name of the vendor is now included in the description of requisitions derived from mobile punchout orders.

Reason for the Change

To help users more easily identify their punchout requisitions.

Customers Affected

Users of the Ordering app who place Punchout orders.

Release Note Info/Steps

When creating a requisition from a Punchout session in the Ordering app (as per these previous release notes) the name of the vendor will now be included in the requisition description, making it easier to identify such requisitions.

Fig.5 - Vendor name shown in the requisition description