Skip to content
Discuss your warehouse
Early product · Evaluation by agreement

Product overview / What Quark does

Know the scope. Evaluate the operation.

Explore Quark’s warehouse operations and the questions to bring to an evaluation. Quark is an early-stage WMS: the operations and interfaces available for your project are agreed against the current build and your requirements.

Capability scopeWhat to evaluateFuture vision

Capability map

One core. Connected operations.

A conceptual overview of Quark WMS — how the warehouse flow and the capabilities that support it share one core. Select a domain to jump to its module.

AWarehouse operations

Receiving → Inventory → Fulfilment, in sequence

Inbound operations

Control goods from arrival to storage.

  • Receiving
  • ASN / inbound flow
  • Putaway
  • Replenishment

Inventory control

Know what's available and where.

  • Real-time inventory
  • Lots, batches, expiry
  • Count & adjustments
  • Traceability

Outbound operations

Move demand through fulfilment.

  • Allocation
  • Picking
  • Packing & sorting
  • Shipping / loading

BSupporting capabilities

Serve every step of the flow

Warehouse execution

Guide operators through their work.

  • Web workspace
  • RF web client
  • Legacy RF support
  • Voice picking
  • Android / mobile

Platform & configuration

Adapt workflows and interfaces.

  • Metadata-driven UI
  • RF screen designer
  • UI metadata designer
  • Roles & permissions
  • Extensible workflows

Integrations & reporting

Connect warehouse information with other systems.

  • API / iPaaS
  • Marketplace & ERP
  • Operational reports
  • Report designer
  • ZPL labels
  • Capability
  • Connected to the shared core
  • Future vision

Conceptual overview — not a release list.

From receipt to a location.

A receipt is only useful when the stock identity and its destination can be followed.

Capability scope Scope

  • Receiving goods and recording receipts
  • Putaway destinations and stock placement

What to evaluate Checks

  1. Confirm the received quantity and stock identity.
  2. Review the destination and check the resulting stock.

Understand stock in context.

A quantity alone does not explain where stock is, its identity or why it is held.

Capability scope Scope

  • Stock balances and movement records
  • Holds, lots, serial numbers and containers
  • Inventory counts and stock adjustments
  • Replenishment planning and execution

What to evaluate Checks

  1. Inspect the location, owner, SKU and relevant stock identities.
  2. Relate a balance or hold to its operation history.
  3. Review count, adjustment and replenishment requirements.

Connect the order to execution.

Allocation, picking and shipping need clear handoffs and visible exceptions.

Capability scope Scope

  • Allocation and stock reservation
  • Picking review and completion
  • Packing workstations and carton completion
  • Dispatch and loading

What to evaluate Checks

  1. Examine the demand, reservation and remaining quantity.
  2. Follow completion and the handoff to the next operation.
  3. Define the checks between loading and goods issue.

Give each action a clear context.

Operators and supervisors need to know which task they are doing and what happens when it cannot be completed.

Capability scope Scope

  • RF terminal workflows
  • Task ownership, progress and handoffs

What to evaluate Checks

  1. Review the operator journey on the relevant RF interface.
  2. Check task ownership, progress and exception handling.

Evaluate how the setup changes.

A process change needs an identifiable owner, a clear version and a checked operational effect.

Capability scope Scope

  • Metadata Studio and configuration management
  • Report definitions and templates
  • Integration-event visibility

What to evaluate Checks

  1. Ask to compare one supported configuration change before and after use.
  2. Check a report output against its source data.
  3. Confirm interface ownership, error handling and recovery.

Workflows in context

Bring an operational question.

These examples help frame an evaluation. They describe questions and checks to work through together, rather than a self-service product demonstration.

Workflow example

Investigate a stock balance.

A supervisor needs to understand why stock in a location is unavailable.

Warehouse goal
Identify the stock and explain the state that the operator sees.
What to check
A clear set of facts to discuss: which stock is involved, what happened and what still needs investigation.
  1. Step 1Find the relevant owner, SKU, location and lot or container.
  2. Step 2Review the displayed hold context and relevant movement history.
  3. Step 3Check that the recorded operation explains the balance.

Workflow example

Review demand and allocation.

An order has partially allocated demand. A further allocation needs to be understood.

Warehouse goal
Compare the reserved stock and remaining demand before and after the operation.
What to check
An explicit reservation change and any remaining demand. Picking and shipping are separate steps to examine.
  1. Step 1Review the demand and its current reservation.
  2. Step 2Follow the agreed allocation scenario in the available build.
  3. Step 3Compare the resulting reservation and remaining demand.

Workflow example

Evaluate a process change.

A warehouse process needs a change in its supported configuration.

Warehouse goal
Understand the change, who owns it and how its effect is checked.
What to check
An agreed before/after evaluation, with responsibilities and any development needs made clear.
  1. Step 1Describe the current operation and expected difference.
  2. Step 2Identify the supported setting, its version and the steps needed to apply it.
  3. Step 3Repeat the same operation, compare the result and discuss how to restore the prior setup.

Plan the evaluation

Confirm the fit before making commitments.

Availability, project scope, device compatibility and individual connections are confirmed during evaluation.

Define your scope

Bring your processes, stock identities, users and device requirements. Agree the relevant checks and open gaps before a rollout.

Prepare with the Readiness Assessment

Check change and connections

Review supported configuration changes and report outputs. Confirm each ERP, carrier or automation connection individually.

Plan your WMS budget
Future vision

Keep the Vision in view

AI Harness, AI Onboarding and AI Support belong to the long-term Vision and are not current product capabilities.

Read the long-term Vision

Let’s evaluate the fit

Start with your warehouse.

Describe your operation and review the available build together. Agree on scope, open requirements and success criteria before making implementation commitments.

Discuss your warehouse Plan your budget

You do not need to provide operational data to explore this overview or use the WMS cost planner.