Accelerators

Accelerator · Installs into a tenant

Receiving Through Shipping, Module By Module

The WMS Accelerator covers the warehouse end to end — inbound receipt, inventory tracking, picking and packing, outbound shipping and cycle counting. This publication unpacks it into its 15 modules, so the flows behind each operation can be read before they are installed.

15 modules52 data models49 data flows43 screens6 document designs

What it does

The Warehouse, End To End

Fifteen modules, each owning one part of the movement of goods through a site.

Receiving

Inbound orders received against expected quantities, with the discrepancies recorded rather than silently absorbed.

orderReceiving · 11 components

Inventory tracking

Split, move and adjust inventory with every change written to history — the largest module in the package alongside cycle counting.

inventoryTracking · 14 components

Cycle counting

Scheduled and ad-hoc counts with variance capture, so accuracy is measured rather than assumed.

cycleCounting · 14 components

Picking and packing

Pick lists worked from the floor, then packed into containers tracked through to the shipment.

picking · packing · 14 components

Shipping and logistics

Outbound shipment build, carrier handoff and the documents that travel with the goods.

shipping · logistics · 18 components

Site and configuration

Storage zones, units and locations — the structure everything else is organised within, and which an MES Area Map can auto-create.

siteManagement · configuration

Modules

Published As Components, Not A Blob

A .fuuz package is a single archive. This publication unpacks it into one directory per module, so a change to a flow reads as a change to a flow.

15Modules
52Data models
49Data flows
43Screens
ModuleComponentsContains
configuration
Configuration
21 dataFlows · 1 screens
cycleCounting
Cycle Counting
149 dataFlows · 5 screens
dashboard
Dashboard
21 dataFlows · 1 screens
inventory
Inventory
41 dataFlows · 3 screens
inventoryTracking
Inventory Tracking
146 dataFlows · 8 screens
logistics
Logistics
81 dataFlows · 7 screens
orderProcessing
Order Processing
41 dataFlows · 3 screens
orderReceiving
Order Receiving
115 dataFlows · 6 screens
orderTracking
Order Tracking
33 dataFlows
packing
Packing
54 dataFlows · 1 screens
picking
Picking
95 dataFlows · 4 screens
quality
Quality
22 dataFlows
shipping
Shipping
108 dataFlows · 2 screens
siteManagement
Site Management
11 screens
testing
Testing
21 dataFlows · 1 screens

Why some components sit outside modules/

Only data flows and screens carry a module in the package. Data models, document designs and seed data carry none, so they are filed by type at the repository root rather than assigned to a module on a guess.

Documentation

Read It Before You Install

Shipped with the accelerator, converted to markdown in the repository.

Pairs with MES

If the site also runs the Fuuz MES Accelerator, the WMS Area Map Application Configuration auto-creates matching storage zones and units from the Areas and Workcenters defined in MES. Review it before finishing site setup on either side.

Before you install

A Jump Start, Not A Finished Answer

An accelerator is a pre-built, configurable starting point that addresses the bulk of the common challenges in its domain. It is not intended to solve every possible variation off the shelf — requirements that fall outside it are expected and normal for the model, not a shortcoming of this one.

Standard

Delivered and working as-is. No configuration needed.

Configurable

A base capability you adapt with the platform's own no-code and low-code tools — screen builder, transforms, workflow rules, flow parameters — without professional services.

Custom development

Feasible on the platform but outside this accelerator's current scope. A scoped change through Fuuz or a certified partner.

Once installed, it is yours

Installation forks the flows, models and screens into your environment as your own copies. Later versions published against this accelerator do not propagate to you automatically — picking up a change means deliberately re-applying it.