LISA.EXE v2.0 // MISSION LOG
--:--:-- NL / EN
◂ BACK TO MISSIONS
StoreAssist — mission banner with the title and pixel art in the same style as the other missions
MISSION_003 ✓ DONE ★★★ +2800 XP
StoreAssist — from tally list to pallet, in one app

The more complex follow-up to FieldAssist: one app for stocktaking, picking, packing, and printing, built while a major client co-funded and shaped it.

[ROLE]
Product Designer
[DURATION]
Apr – Aug '26
[TEAM]
1 designer · dev team
[TOOLS]
Figma
// LOG_ENTRY — BACKGROUND

Same necessity, a bigger job

The same technical necessity as FieldAssist: outdated hardware that could no longer be updated. StoreAssist followed FieldAssist — with considerably more complexity under the hood.

// LOG_ENTRY — THE BRIEF

One app for four kinds of work

Rebuild StoreAssist into the tool for warehouse and store staff: stocktaking, picking, packing, and printing — four flow families that need to work both on their own and seamlessly into one another.

// LOG_ENTRY — CLIENT CONTEXT

One client funded it, everyone had to benefit

PLOT TWIST

StoreAssist was already on the roadmap, but along the way it also became a paid client project: a major client bought hours and had their own stakes in how the app would work. At the same time, a broad rollout to all customers was always the goal. That tension — one paying client versus a broad customer base — runs like a thread through the obstacles, principles, and reflection below.

StoreAssist: the Packaging step when packing a shipment, with a 150cm-tall pallet and one box next to it The Packaging step: pallet with height, next to loose boxes — the client-specific request that made the tension concrete
// LOG_ENTRY — THE FLOWS

Four flow families, each with its own entry points

Checking and correcting have been merged into one flow — stocktaking — with two very different entry points. Together with picking, packing, and printing, that makes four flow families.

StoreAssist: Tally list TL00043 for Groot Magazijn, 14 of 246 items counted, with a list of TestArtikelTA1 lines per location
01
Stocktaking

Checking and correcting stock, through two very different entry points.

With tally lists — guided
Ad hoc — single item
StoreAssist: Collecting screen for pick list P000026, with Aikon Lounge sofa and 1.5-seater including expandable configuration lines
02
Picking

Collecting products for an order — organization-dependent.

With warehouse locations
Without warehouse locations
Directly at the truck
Via a packing station
StoreAssist: Packing checklist for shipment L0000562 with plants like Monstera and Strelitzia, each with a quantity to check off
03
Packing

From a refined checklist to full materials registration.

Checklist — everything is already laid out
Materials registration — boxes/pallets incl. pallet height
Quick pack — shortened, inside the pick flow
StoreAssist: Layouts screen with the choice between Price card A5, Price card A6, Price list, Shelf label 50x14, and Shelf label 75x25
04
Printing

Labels and stickers, for store and warehouse.

Labels — for the store
Stickers — for the warehouse
CORE RULE

Every flow must be able to run on its own and be part of a larger chain — without the app feeling like a different product per organization configuration.

StoreAssist: input screen for counting, with item, location, and stock at the top and a large plus/minus counter below Counting in practice: item, location, and stock at a glance, with a simple plus/minus counter
// SIDE_QUESTS — OBSTACLES ALONG THE WAY

The obstacles along the way

One flow, two entry points

Stocktaking has two very different entry points: guided via tally lists, or ad hoc for a single item.

Organization-dependent variants

Picking works differently per organization: with or without warehouse locations, directly at the truck or via a packing station.

Complexity compared to FieldAssist

Where FieldAssist was a largely linear system, StoreAssist branches into four flow families that still need to feel like one whole.

Collaboration with multiple LogicTrade modules

StoreAssist touches not one, but several modules in the wider system.

Potential handover to FieldAssist

After picking or delivering, the process can flow into FieldAssist — the two apps had to connect seamlessly.

One client funded it, all clients had to benefit

The interests of the paying client and those of the broader customer base didn't automatically align.

// LOG_ENTRY — PRINCIPLES

The same guiding principle as FieldAssist, but not the same solution

01
"FOR YOU" AS A PRINCIPLE, NOT A COPY

Translated to StoreAssist's own reality, not blindly copied from FieldAssist.

02
PRE-SELECTION INSTEAD OF ONE OVERVIEW

Four flows are too different for one list — choose first, then enter the flow.

03
SCANNING AS ITS OWN MENU ITEM

Via device camera, PDA scanner, or external scanner — scanning is needed everywhere, so it gets its own place.

04
FLOWS CONFIGURABLE PER ORGANIZATION

An administrator or consultant turns flows like packing on or off; everything is on by default.

StoreAssist: the For You home screen with four tiles — Collect orders, Pack orders, Count stock, and Print price cards — each with a badge for the number of open tasks Pre-selection in practice: four tiles, no overcrowded list
// LOG_ENTRY — TIMELINE

From beta to final version

APR '26
Project started — version 1
JUN '26
Version 1 delivered as beta
JUN–AUG '26
Feedback from the beta processed into version 2
AUG '26
Version 2 — final version live
// LOG_ENTRY — RESULT

Four flows, one app that holds together

STRAIGHT TO
WORK
major client could start working with the delivery right away
4 FLOW
FAMILIES
usable individually and together
ONGOING
COLLABORATION
for additions and fixes ever since
// LOG_ENTRY — REFLECTION

What I take from this

Specific isn't the same as wrong

The extensive packing flow with pallet height wasn't a strange or odd request, but a very specific business flow relevant to only a small part of the customer base. The real tension was in the risk that such a specific flow, made too prominent, would make the app feel unnecessarily complicated for the "average" client. Solved by keeping the extensive flow while adding a quick variant ("quick pack") in the pick flow, and by making flows configurable per organization — instead of choosing between "the client" and "everyone else".

StoreAssist: the Review screen after collecting pick list P000026, with the toggle Pack and complete versus Only complete collecting The "quick pack" toggle: straight from the pick flow, without needing to enter the extensive packing flow
◂ PREVIOUS MISSION 3 / 4 NEXT MISSION ▸