What it proves
Enterprise warehouse-to-delivery documents from structured application data.
Teleza does not replace a WMS, TMS, carrier platform, customs platform, inventory system, or proof-of-signature authority. It renders documents from logistics records your application already controls.
Pick, pack, ship
Order number, warehouse, SKU, carton, carrier, tracking, and label fields stay together across warehouse and customer documents.
Delivery proof
Driver, vehicle, receiver, item condition, and exception notes can be rendered consistently without manually assembling packets.
Enterprise controls
Tenant isolation, audit fields, exception handling, and private-cloud evaluation are visible in the pack manifest and checklist.
Enterprise controls
- Tenant-scoped API keys, report definitions, and generated documents.
- Reserved audit fields for order, label, pick, pack, delivery, return, warehouse transfer, receiver, and custody events.
- Exception coverage for damaged, short, delayed, returned, warehouse-transfer, and cross-border handoff scenarios.
- Private-cloud deployment path for regulated shipment and customer data.
- Evidence-gated claims through the logistics pack test script and rendered sample assets.
System boundaries
The sample data is fictional; real deployments need tenant-scoped data, retention review, carrier/customs boundaries, and customer signoff.
Operational ownership
Your OMS, WMS, TMS, carrier, customs, route, signature, and inventory systems remain the source of truth.
Audit readiness
Document IDs, operators, drivers, receivers, warehouses, tracking references, and custody events are explicit in the evaluation contract.
Enterprise evaluation standard
This pack is ready for enterprise evaluation when a design partner can inspect ten rendered PDFs, review the data contract and enterprise controls, search the gallery for logistics or fulfillment, understand the WMS/TMS/carrier/customs/signature boundary, and run the local demo script without relying on hosted seed identifiers.
- Ten rendered PDF and HTML samples are published.
- The samples use one coherent warehouse-to-delivery shipment scenario.
- Carrier and proof-of-signature responsibilities remain explicit boundaries.
- Dispatch, returns, warehouse-transfer, and cross-border handoff examples are covered.
- Private deployment can support data-sovereignty conversations without claiming WMS or TMS replacement.
Shared data contract
The beta pack keeps the first integration predictable with a narrow field contract: order, label, packing slip, pick list, delivery note, issue slip, carrier, tracking, route, warehouse, wave, picker, recipient, address, driver, vehicle, receiver, custody event, retention class, integration reference, and item fields for SKU, description, quantity, carton, unit, batch, exception, and condition.
Logistics & Fulfillment Mini Pack
These ten templates are existing rendered outputs from the starter catalog. Each sample links to the PDF, HTML preview, and full gallery entry for the same template key.
Shipping Label 4x6
Carrier-style parcel label with service, tracking, package, sender, and recipient fields.
Standard Packing Slip
Customer-ready package contents document with cartons, recipient, and order detail.
Single Order Picking Slip
Warehouse pick list with aisle, bin, SKU, quantity, wave, and picker fields.
Proof Of Delivery
Driver, receiver, vehicle, item condition, and exception detail for delivery handoff.
Goods Received Note
Receiving and exception review note for store, warehouse, or 3PL handoff workflows.
Dispatch Note
Outbound warehouse handoff document for dispatch desk and route preparation.
Standard Delivery Note
Customer-facing delivery note for shipped goods, handoff, and recipient signoff.
Return Delivery Note
Reverse-logistics document for returned goods, condition notes, and warehouse handoff.
Warehouse Transfer Issue Slip
Internal transfer control for moving stock between warehouse areas or cost centers.
Cross Border Delivery Note
Shipment handoff note for cross-border logistics review without claiming customs filing authority.
Best fit
This pack is strongest for SaaS builders and operations teams who already collect order, pick, pack, route, shipment, and receiving data and want reliable customer-facing labels, PDFs, and spreadsheet outputs.
Not a WMS or TMS
Teleza automates generated documents from structured records. It does not provide inventory authority, routing, carrier label validation, customs filing, live tracking, signature capture, or warehouse task orchestration.