Warehouse and logistics software · Hong Kong

Software for the businesses that move goods.

Warehouse, inventory, fulfilment, and logistics systems on one set of records — configured to your operation and connected to the software you already run.

Describe your project See how exceptions are handled
Cloud or on-premise Barcode and mobile floor operations Northpoint Enterprises Limited, Sheung Wan
Workflow preview Site HK-01 · Shift 07:00–15:00

Inbound receipts

4 open
RCV-204118 palletsChecked in
RCV-20426 palletsPut-away
RCV-20432 cartonsHeld
RCV-204411 palletsBooked

Stock by location

Sample state
A-02-14SKU 44120312 ea
A-04-07SKU 4412096 ea
B-11-02SKU 7188048 ea
STAGE-3Mixed7 pallets

Pick queue

3 in progress
PK-883114 / 17 lines
PK-88325 / 11 lines
PK-88331 / 8 lines
PK-8834Queued22 lines

Exceptions

2 to clear
Short pickPK-8832
Receipt heldRCV-2043
Count varianceCleared
Address checkCleared

Dispatch

Cut-off 16:30
Packed 24 Labelled 19 Awaiting carrier 5 Collected 11

Receiving

Bookings, checks, put-away

Inventory

Items, locations, lots, counts

Picking

Allocation, directed picks, packing

Dispatch

Consignments, carriers, proof

Reporting

Live operational records

Interfaces

Inbound and outbound data exchange

Exception queue

Four exception types and the record path for each.

Select a case to see the records it writes.

Open cases04

Duplicate entry between systems

Interfaces

One system captures the record; the others receive it. The second keying is removed rather than made faster.

Order channel Interface Northpoint order record Pick Finance posting
System boundary affected

Between the channel or finance system and the warehouse order record.

Exceptions raised at the point of work

Picking · Dispatch

A short pick, held receipt, or failed delivery is written as an exception when it happens, and sits in a supervisor queue until cleared.

Directed pick Exception raised Supervisor queue Resolution recorded Dispatch
System boundary affected

Between the floor and the office — the same record serves the handheld and the supervisor view.

Stock held as movements, not as a file

Inventory

Each receipt, move, pick, and adjustment writes to the stock record, with cycle counting in place of periodic full counts.

Receipt Stock movement Location balance Cycle count Reporting
System boundary affected

Between the stock movement and the location balance.

One configured process across sites

Warehouse

Sites run the same workflow, with the differences between them held as configuration rather than as separate installations.

Site A process Shared workflow Site B process One record set
System boundary affected

Between sites — per-site and per-client rules become configuration on one platform.

Platform

Modules.

Warehouse management

Floor operations
Operational users

Receiving staff, put-away and pick operators, supervisors, dispatch.

Core records

Receipts, locations, stock movements, pick tasks, consignments, exceptions.

Supported workflow
  • Booking and goods-in check
  • Directed put-away and replenishment
  • Pick, pack, and dispatch confirmation
Warehouse management in detail

Inventory control

Stock authority
Operational users

Stock controllers, purchasing, finance, site managers.

Core records

Item master, locations, lots and serials, adjustments, transfers, counts.

Supported workflow
  • Movement-level stock keeping
  • Cycle counting and variance review
  • Multi-site transfers and balances
Inventory control

Order fulfilment

One queue
Operational users

Customer service, fulfilment and dispatch teams, account managers.

Core records

Orders, allocations, pick and pack confirmations, carrier hand-offs, returns.

Supported workflow
  • Capture from the channels you sell through
  • Allocation against available stock
  • Pack confirmation and hand-off
Order fulfilment

Logistics

Outbound
Operational users

Transport planners, dispatch coordinators, depot managers.

Core records

Consignments, loads, routes, driver or carrier assignment, delivery status.

Supported workflow
  • Consignment creation from dispatched orders
  • Load and route planning
  • Status returned against the order, where carriers support it
Logistics

Data exchange and reporting

Interfaces
Operational users

Operations and supply chain managers, finance, whoever owns the adjoining system.

Core records

Inbound orders, stock positions, accounting entries, shipment updates, audit trails.

Supported workflow
  • Deciding which system owns each record
  • Scheduled or event-driven exchange
  • Reporting across the combined records
Data exchange and reporting

Custom development

Scoped work
Operational users

The process owner, plus the people who will use it daily.

Core records

Whatever the process requires, specified with the people who do the work.

Supported workflow
  • Requirements captured on the floor
  • Build, test, and deploy against them
  • Change as the operation changes
Custom development
Architecture

System architecture.

One record set in the middle; defined interfaces to what is either side of it.

Order channels

Orders in, status back — web store, marketplace, ERP, or customer file.

Finance systems

Goods received, shipped, and adjusted, in a form finance can post.

Northpoint

One data model for sites, stock, locations, and orders.

  • Configured workflows
  • Role-based access and audit trails
  • Reporting on live records

Barcode hardware

Handheld terminals, scanners, and label printing on the floor.

Carriers

Consignment details out, delivery status back where supported.

Configuration

Operating profiles.

Third-party logistics

Many clients, one floor
Pressure point

Every client wants its own rules, and every depot has drifted into its own process.

Held as configuration

Client accounts, storage and handling rules, labelling, and reporting formats.

Records that matter

Stock by client and location, activity per account, exceptions by site.

Logistics companies

Distributors and wholesalers

Stock balance
Pressure point

Stock is committed across channels before anyone can see what is actually available.

Held as configuration

Allocation rules, reorder levels, customer-specific pricing references and pack rules.

Records that matter

Available-to-promise, movement history, cycle-count variance, order lines per run.

Distributors

Manufacturers

Materials to finished goods
Pressure point

Materials, work in progress, and finished goods are tracked in different places.

Held as configuration

Location types, consumption points, lot and serial traceability requirements.

Records that matter

Material issues, output receipts, traceability from lot to shipment.

Manufacturers

Retailers

Store and online
Pressure point

Store and online demand draw on one stock pool through two separate routes.

Held as configuration

Channel priority, dispatch cut-offs, packing and returns handling per channel.

Records that matter

One stock position, one fulfilment queue, returns back against the original order.

Retail businesses
Delivery

Deployment.

01

Discover

Your process walked through on the floor and written down as a requirement.

Requirement signed off

02

Design

Workflows, locations, roles, and interfaces designed against that requirement.

Design approved

03

Build and validate

Your team runs real scenarios on your own data before anything goes live.

Acceptance by your team

04

Deploy

Data migration, training, and a planned go-live, site by site where there are several.

Go-live agreed

05

Support

Support for the live system and changes as the operation changes.

Arrangements agreed with you

How we work, stage by stage
Workflow previews

Configured workflows.

WF-01 · Multi-site 3PL on one platform

Logistics
Input
  • Goods-in scan at any depot
  • Client account on the receipt
  • Per-client rules held as configuration
System action
  • Same receiving, picking, and dispatch workflow at every site
  • Client rules applied as configuration, not a separate installation
  • Exceptions routed to the site supervisor queue
Recorded output
  • One record set across depots
  • Activity per client account
  • Exceptions per site in one queue

WF-02 · Store and online into one fulfilment queue

Retail
Input
  • Orders from store and online channels
  • One stock pool
  • Allocation and cut-off rules per channel
System action
  • Both channels feed one queue with directed picking
  • Allocation against available stock
  • Pack confirmation and carrier hand-off in the same step
Recorded output
  • One stock position behind both channels
  • Dispatch confirmation per order
  • Returns recorded against the original order
Implementation notes

Workflows above are configurations, not accounts of named client engagements.

Interfaces depend on the access and data your existing systems provide; the architecture categories are kinds of information we work with, not ready-made connectors or certified integrations.

Movement-level stock keeping requires a maintained item master and an agreed location scheme. Carrier status is returned where the carrier supports it. Hardware and scope are agreed per project.

Contact

Start a project.

Name, email, and the process description are required. The rest can be left blank.

Intake Replies from info@northpointhk.com
Contact details

We use what you send to reply to your enquiry.