Smart PackMANIFEST EXCHANGE

LIGHTWEIGHT MANIFEST EXCHANGE

Every box,
a clearer handoff.

Let box contents reach the receiving team in advance. Connect packing and receiving with SSCC manifests, JSON and local-first workflows.

Explore the workflow Discover self-hosting

IN DEVELOPMENT · Product concept and design goals

DESIGNED AROUND A CLEAR HANDOFFOffline workflowsShareable manifestsData under your control

01 / THE WORKFLOW

The manifest moves first. The team gets ready.

A lightweight manifest “post office” connects supplier and customer applications. The platform handles storage and exchange while each local app keeps its own workflow.

SELECT A STEP TO EXPLORE

Pack a box. Keep its manifest.

Keep box JSON and pending uploads on the workstation. Preallocated, valid SSCC ranges enable offline numbering.

No continuous connection required
manifest.jsonJSON
{
  "sscc": "<SSCC>",
  "manifestVersion": 1,
  "items": [
    {
      "sku": "DEMO-001",
      "quantity": 12
    }
  ],
  "delivery": "Pending upload"
}

Local illustration — no business service connected

02 / THE PRODUCT

The essentials, kept lightweight.

Start with a single manifest. Reserve room for pallets, shipment batches and printed packing lists. These planned capabilities will be delivered in stages.

01

One box. One SSCC.

Link each box to its JSON manifest: products, quantities and serialized item identifiers. Share one manifest between supplier and customer.

SSCC + JSON
02

Boxes, pallets and batches

Reserve versioned box-to-pallet and pallet-to-shipment relationships. Expand references for summaries without duplicating every item.

Lightweight relationships
03

Turn JSON into a packing list

Generate labels and A4 packing lists from the same data source, with box, pallet and batch views, version references and totals.

Labels / A4 / PDF

STRUCTURE WITHOUT DUPLICATION

▦
Shipment batchbatchId
↳PalletpalletId
↳BoxSSCCJSON

Reference members and versions, with room to trace splits and regrouping.

ONE DATA SOURCE, ANOTHER VIEW

A clear A4 packing list.

Expand by box, pallet or batch. Pin the version, total by unit and use complete local data for offline output.

03 / BUILT TO CONNECT

Your application.
Your way of working.

Connect your own packing workstation, receiving app or PDA through platform Tokens and SDKs. Keep the interface your team knows, and exchange data within explicit permissions.

HTTPSTokenJSONSDKs planned
YOUR APPLICATIONWorkstation / PDA / Web
HTTPS + TOKEN
Smart PackIdentity · Authorization · Manifest storage

Independent accounts. Per-device grants. Separate credentials for senders and receivers.

04 / YOUR OWN INSTANCE

A smaller footprint.
An independent instance.

Use a hosted service or deploy on your own cloud server. The business platform is designed for few dependencies, verifiable backups and recovery, with service endpoints under your control.

SELF-HOSTING DESIGN · PLATFORM IN DEVELOPMENT
01

One lightweight application

A Java backend and Vue management interface, organized as one application.

02

One persistent data directory

Manifest JSON, permissions and acknowledgements, with embedded storage and consistent backups planned.

03

Accounts of your own

Username, password and image CAPTCHA. Independent tenants, with no required Cloud identity service.

A FEW DETAILS

Before you start,
a few details.

Is this a full warehouse or ERP system?

Smart Pack focuses on manifest storage, authorized exchange and retrieval. Customer applications handle inventory, ERP receipts and other business processes. A cache acknowledgement is not a goods receipt.

Does it require Cloud login or MQTT?

This website needs no login. The business platform is designed with independent accounts, using its own username, password and image CAPTCHA. HTTPS is the default interface; MQTT is optional.

Can our own workstation or PDA app connect?

That is a core design goal. Keep your own interface and workflow, and integrate through platform Tokens and SDKs. Each account is its own tenant and can act as both customer and supplier. The first SDK is undergoing internal validation and is not publicly released.

Can I download, self-host or get the source today?

The product is in development and being prepared for internal business validation. The repository is private, with no public business installer or SDK yet. Independent deployment is a design goal; release details will follow.

LET’S MAKE THE HANDOFF SIMPLER

Start with your packing workflow.

Let’s talk about manifests, receiving workflows and application integration.

Get in touch