PICK, PACK AND SHIP
Brief

Goal
Accelerate the delivery of enhancements to move from 25-30% (projections) of customers Live with MA to 50% by the end of the year. In parallel, increase the number of customers using Mobile Automation.

How
We use a heat squad with committed members for 5 days: 1 UX, 1 FE platform, 2 developers (Logistics), 1 PBA,
1.Squad 1-Improve the flow of 3 transactions, starting with the pick ticket
2.Squad 1-Improve the look & feel of Mobile automation

Research

OBJECTIVE: Deliver an initialised and working version

MAIN FOCUS AREAS:

Redesign the menu and submenus
 – Improve navigation and structure for a better user experience.

Preparation Slip → Picking Process
 – Transition or link the preparation slip phase directly to the picking step.

Improve UI and Visual Design
 – Enhance the look and feel of the Mobile Automation interface.

Use Composite Codes on Pick Tickets
 – Possibly implement barcode or grouped product codes for efficiency.

Avoid Adding Products Manually
 – Do not allow manual "Add a product" during the process.

Scenario to Cover:
 – When receiving an order: Scan/read the item, mark it as received


Modification on global allocation flow

NEW

Global allocation won’t stay purely “hands-off” anymore. Operators will soon have the option to confirm (not choose) the lot and/or serial number, depending on how the manager has parameterised X3.


BEFORE

As an operator, I need to scan the pick ticket and confirm the quantities picked, so that the system can automatically allocate stock from available locations.”

AFTER (with new option)

As an operator, I need to scan the pick ticket, confirm the quantities picked, and, if required by configuration, validate the lot and/or serial number, so that the system ensures the right stock is allocated automatically.

Scan on smart phones


Picking with global allocation
Goal: System decides stock to allocate, operator just confirms what they pick
Actors: manager (config), operator (execution)
Goal: operator picks entire order(s) without worrying about stock details.

Steps
Manager setup
Manager configures order lines as “Global allocation.”
Stock is reserved in bulk by the system.

Operator login / Home screen
Logs into X3 Mobile Automation.
Selects Picking module.
Pick ticket selection
Operator scans or searches for pick ticket (or composite code).
System shows list of orders to pick (allocated globally).

System assigns stock
System proposes the products to pick (quantities + location zone).
No lot/serial/emplacement decision for operator — just execute.

Operator executes picking
Operator goes to suggested location(s).
Scans product(s).
Confirms picked quantity.

Validation
System validates against global allocation.
If qty matches, move is confirmed.
If discrepancy, operator can adjust → system reallocates globally.

End of process
Operator confirms completion.
Stock updated, order flagged “picked.”

Key point: operator follows a simple flow: scan → confirm quantity → done.

Goal: stock is reserved by lot/serial/emplacement in advance. Operator must pick exactly those.

Actors: manager (config), Operator (execution)
Goal: Operator picks exact lots/serials/emplacements as pre-allocated.

Steps

Manager setup
Manager configures order lines as “Detailed allocation.”
Each line is pre-assigned with lot / serial / location / emplacement.
Operator login / Home screen
Logs into X3 Mobile Automation.
Selects Picking module.
Pick ticket selection
Operator scans or searches for pick ticket (or composite code).
System shows list of orders to pick (detailed allocations).

Goal: stock is reserved by lot/serial/emplacement in advance. Operator must pick exactly those.

System displays detailed instructions
For each line, operator sees:
Product code (FBEV09030001)
Lot (LOT25090500107)
Location (STO01)
Emplacement (bin/shelf)

Operator executes picking
Operator goes to the exact emplacement.
Scans product/lot.
Confirms picked qty (must match detailed allocation).

Validation
If correct lot/serial/emplacement scanned → validated.
If mismatch → system rejects, operator must scan the right one.

End of process
Operator confirms completion.
Stock updated, order flagged “picked.”


Key point: operator follows a guided flow: scan product → validate against exact lot/emplacement. No flexibility.


​​​​​​​


Action

Secure Operator Input (Lots, Serial Numbers, Locations)
Use colour-coded tags for Lot / Serial / Location (example: Lot = blue, Serial = red)
Apply sticky headers or icons on repeat values to reduce visual overload

Validation Before Submission
Add inline validation (green check/red X) next to each Lot/Serial input
After user enters data, add a review step before hitting "Submit"

Composite Code Option
In Global Allocation, add a composite scan input at the top of the stock list
When scanned, auto-select the line, pre-fill quantity, and jump to next line
Display "Parsed fields" in a summary pop-in for user confirmation

Workflow Simplification
Add a step counter or progress indicator ("2 of 5 lines picked")
Let user sort stock lines by location to optimise walking path
Use cards instead of full-page blocks for better screen division

1. Secure the operator's work by displaying important information: visualisation of the Lot, Serial Number and location.
UX: Propose the best approach for displaying this information on a small screen that already contains a lot of information
Frontend platform: Provide the components designed by UX available.
Application team: Apply the UX design with the platform components provided


2. Secure the operator's work by controlling and validating the lot, location and Serial Number. Not requesting a control scan increases the risk of inaccuracy and weakens stock validation.
UX: Propose the best way to check information before it is validated, considering the small size of the screen.
Insert this action into the workflow.
Frontend platform: Make the components designed by UX available.
Application team:
Add a new parameter to the Mobile Automation settings. Parameter for operator action control request, which consists of validating by scanning the lot, location and Serial Number.
Apply the UX design with the platform components provided.

3. Add the option to use composite code
UX: Propose the best design to combine the option to use composite code in detailed allocation with the control in point 2
Frontend platform: Make the components designed by UX available
Application team: Apply the UX design with the platform components provided

4. Improve and simplify the transaction workflow
UX: Consider the two types of allocations (link to the Stock allocation documentation)
Make the transaction steps smooth and simple for the operator
Make the screens as light and readable as possible
Add the ability to sort by location
Frontend platform: Provide the components designed by UX
Application team: Apply the UX design with the platform components provided

Update the Mobile Automation look & feel
UX: Apply the official Sage guidelines
Update (if necessary) and apply the work done earlier for the flow between pages, from menu to submenu, and the flow from one page to another
Update the menu and Submenu
Add the ability to view a screen containing transactions authorised for the user (without getting through the sub-menu)
Frontend platform: Provide the components designed by UX
Application team: Apply the UX design with the platform components provided






↑Back to Top