Sea Export · WWG Consolidators
Customer Self-Service Shipping Portal
A shipper-facing web portal that captures sea export shipment data at source, lets WWGC verify it, and delivers clean, validated data to the overseas agent in their preferred format — file, API or EDI 856 ASN.
Stack
ASP.NET · SQL Server
Hosting
Windows / IIS
Data model
HBL → PO → SKU
Delivery
sFTP · API · EDI 856
How it works
From shipper entry to verified data — one clean flow.
The shipper owns data entry, WWGC owns verification, and the agent receives only approved, structured data. Every step is tracked and time-stamped.
Shipper logs in
Each shipper / supplier gets secure, role-based access scoped to their own shipments.
Compose entry (Draft)
Tabbed House B/L form captures the full sea export shipment. Saved as Draft — fully editable.
Submit & lock
On submit, the record locks (read-only). No further edits without WWGC re-opening it.
Auto e-mail notice
Notification sent to the shipper and to WWGC the moment a shipment is submitted.
WWGC verifies
WWGC team reviews, corrects if needed, and approves the verified shipment record.
Agent fetches data
The overseas agent (SupplyX) pulls verified data via file, REST API or EDI 856 ASN.
Optional: WWGC booking lane
WWGC can additionally import bookings (Excel) → confirm booking → generate a loading program → feed straight into the compose flow — mirroring the proven process already running in the existing e-HBL system.
Screen layouts
Every screen built around how your team actually works.
Clean, guided screens carrying the full field set of a House B/L, plus dedicated PO and product grids. Indicative mock-ups below.
WWGC Sea Export Portal
Sign in to manage your shipments
Trouble signing in? Contact the WWGC team.
New Sea Export B/L
Record #DRF-100917 Draft
Purchase Orders
+ Add PO| PO Number | Cartons | Volume (CBM) | Gross Wt (KGS) |
|---|---|---|---|
| PO-88231 | 1,200 | 18.40 | 9,650 |
| PO-88247 | 800 | 11.20 | 6,300 |
Products / SKUs
+ Add product| PO | SKU | Material | Style | Size | Qty | CBM | Gross Wt |
|---|---|---|---|---|---|---|---|
| PO-88231 | SKU-44102 | Cotton Jersey | Crew Tee | M | 600 | 9.10 | 4,820 |
| PO-88231 | SKU-44103 | Cotton Jersey | Crew Tee | L | 600 | 9.30 | 4,830 |
| PO-88247 | SKU-51980 | Fleece | Hoodie | L | 800 | 11.20 | 6,300 |
I certify that the information entered above is complete and correct.
Submitted B/Ls
Your submitted shipments
Record WWG-SEA-25-00917 submitted & locked
Submitted 10-Jun-2026 14:32 · No further edits allowed · Awaiting WWGC verification.
| Record No | WWGC Booking No | Notify | Packages | Destination | Gross Wt | Issue Date | Status |
|---|---|---|---|---|---|---|---|
| WWG-SEA-25-00917 | BKG-7741 | ACME Stores GmbH | 2,000 | Hamburg | 15,950 | 10-Jun-2026 | Pending verify |
| WWG-SEA-25-00891 | BKG-7702 | OTTO Group | 1,450 | Bremerhaven | 11,200 | 08-Jun-2026 | Verified |
| WWG-SEA-25-00874 | BKG-7688 | Bonprix | 980 | Rotterdam | 7,640 | 05-Jun-2026 | Fetched by agent |
Delivery method
Request
GET /v1/shipments
?status=verified
&since=2026-06-01
Authorization
{
"hbl_no": "WWG-SEA-25-00917",
"container": "MSKU 762341-0",
"vessel": "MSC ALTAIR",
"voyage": "FE418W",
"pol": "Karachi (PKKHI)",
"pod": "Hamburg (DEHAM)",
"etd": "2026-06-14",
"eta": "2026-07-08",
"status": "verified",
"purchase_orders": [
{
"po_no": "PO-88231",
"cartons": 1200,
"volume_cbm": 18.40,
"gross_weight_kg": 9650,
"products": [
{ "sku": "SKU-44102", "style": "Crew Tee", "material": "Cotton Jersey", "size": "M", "qty": 600 },
{ "sku": "SKU-44103", "style": "Crew Tee", "material": "Cotton Jersey", "size": "L", "qty": 600 }
]
},
{
"po_no": "PO-88247",
"cartons": 800,
"volume_cbm": 11.20,
"gross_weight_kg": 6300,
"products": [
{ "sku": "SKU-51980", "style": "Hoodie", "material": "Fleece", "size": "L", "qty": 800 }
]
}
]
} Nested House B/L → purchase_orders → products — the same hierarchy maps to a flat file, CSV, XML or EDI 856 (ASN).
Data architecture
One House B/L, many POs, many SKUs.
The database is built as a true hierarchy from day one — so a single shipment can carry multiple purchase orders, and each PO can carry multiple product lines.
This structure maps directly onto the EDI 856 (ASN) shipment → order → item levels, covering every must-have and nice-to-have requirement without rework later.
House B/L (HBL)
Container · vessel · ports · parties · dates
Purchase Order (many)
PO number · qty · volume · weight
Product / SKU (many)
SKU · material · style · size · qty
Information captured
Everything on the requirements list — covered.
Must-have — shipment details
- Container, House B/L (HBL), Master B/L (MBL)
- ETD, ATD, ETA
- Vessel, voyage, carrier
- Quantity, volume, weights
- Pick-up, POL, POD, drop-off
- Shipper / consignee / notify parties
- All standard House B/L information
Nice-to-have — PO & product
- PO numbers (multiple per House B/L)
- Quantity / volume / weight per PO
- Item / product line details
- SKU, material, style, size
- Quantity / volume / weight per SKU
Connectivity options
Three ways to deliver data — pick one, or combine.
There's no direct database access. Verified data is delivered through a dedicated integration layer in the agent's preferred format.
sFTP File Feed
Fastest to deploy
Scheduled export of verified shipments (CSV / XML / JSON) dropped to a secure sFTP folder the agent polls. Lowest-risk, proven plumbing.
Build estimate: 5–8 days
REST API (pull)
Most flexible
Secured JSON endpoints the agent calls on demand to fetch verified shipments, POs and SKUs — token-authenticated, paged and filterable.
Build estimate: 10–15 days
EDI 856 (ASN)
Retail standard
True ANSI X12 856 Advance Ship Notice, mapped to the agent's spec and tested against their TMS/ERP. Built for retail buyers (OTTO, Bonprix).
Build estimate: 15–25 days
Format-flexible: flat file, CSV, XML, JSON, or a true EDI 856 (ASN) mapped to the agent's specification. A sample output spec is prepared and shared for sign-off before development.
Delivery plan
Indicative effort.
Foundation — required for any option
Database design — HBL → PO → SKU hierarchy
4–6 days
Shipper data-entry portal (full House B/L, multi-PO, multi-SKU)
15–20 days
WWGC verification & approval workflow
8–10 days
User management, roles & security
6–8 days
Foundation subtotal
~33–44 days
Connectivity — add the option(s) you need
sFTP File Feed
5–8 days
REST API (pull)
10–15 days
EDI 856 (ASN)
15–25 days
Estimates are indicative working days for a lean DSS delivery team and firm up once scope is locked. They build on a proven base — the existing e-HBL portal already runs this draft → submit → notify → verify → fetch workflow in production.
Built on a workflow we already run in production.
Dynamic Software Solution has delivered this exact portal pattern for WWGC and its agents. This engagement extends it with a deeper PO / SKU model and a modern data-delivery layer.