🆕 USPS Adjustment Billing

---

USPS Adjustment Billing

Release Date: June 10, 2026

---

What's New

Added support to import Bukuship’s USPS invoice breakdown and create billing adjustments.

---

Why?

All Underpaid items are converted into adjustments so customers can be billed correctly.

---

How It Works

CSV file are uploaded here: Portal: Invoice Upload

• UspsBukushipDetailFileImport creates a record in invoice.import and inserts the CSV rows into invoice.usps_bukuship_detail.
• sp_ProcessUspsBukushipDetails creates the related charges in dbo.charge.

---

🆕 CUSMA White label workflow

---

CUSMA White label workflow

Release Date: June 10, 2026

---

What's New

Added Non-CUSMA white label support in the legacy portal. Admins can enable the functionality on the accounts page.

---

Why?

This feature determines whether a white label or final mile label should be created for US and international shipments based on item origin.

• A white label is created when the shipment contains any item with an origin outside of CA, US, or MX.
• A final mile label is created when all items have a CUSMA origin: CA, US, or MX.

---

How It Works

When enabled, this setting overrides all existing white label generation rules.

For white labels generated under these rules:

• Canadian terminal scan: Allows the scan, records the scan date, and creates milestones. The label is not printed.
• US terminal scan: Allows the scan, records the scan date, creates milestones, and prints the label.

---

🆕 CPSC eFiling and Compliance Support for SKU Management

Release Date: June 5, 2026

---

What's New

The Legacy SKU Management portal now supports a scalable CPSC (Consumer Product Safety Commission) compliance and certificate tracking architecture. By linking CPSC certificates and citations directly to SKU product entities, the platform is prepared to automatically generate PGA (Partner Government Agency) message set data elements for T01/T11 consumption entry clearances.

---

Why?

CPSC eFiling becomes mandatory July 8, 2026 for all CPSC-regulated imports on consumption entries. Custom brokers filing T01/T11 clearances via ACE will require PGA Message Set elements at the time of entry.

By shifting compliance data to the SKU and Certificate layer, the data is reusable across all shipments using the same SKU. The PGA payload can be assembled entirely from the SKU layer without modifying transactional shipment data.

---

How It Works

All CPSC compliance data lives at the SKU and Certificate level. As long as a shipment line item links to a SKU, and that SKU links to a valid certificate, the full CPSC PGA payload is successfully assembled.

The backend database models this using three core entities:

• SKUProduct — Holds basic item identifiers (unchanged).
• SKUProductCertificate — Stores GCC (General Conformity Certificate) or CPC (Children's Product Certificate) fields.
• SKUProductCertificateCitation — Stores regulatory citations (e.g. 16 CFR 1303) per certificate.

During bulk CSV imports, C#-side generated GUID values for certificate primary keys are preserved using SQL Server's KeepIdentity configuration. This resolves relational mismatches between parent certificates and child citations.

---

In-App Compliance Management

Compliance details can be managed directly on the SKU Management page. Clicking the edit button on any SKU opens the Change Sku dialog.

1. SKU Info Tab

Displays vendor references, cost, currency, and origin attributes.

2. Certificate Info Tab

Stores certificate registration identifiers, processing codes, certifier details, and production dates.

3. CPSC & Citations Tab

Manages inspection details, disclaimers, and associated compliance checklist rows. 4225-b1b4-23f4f54d4afc/media__1780637371923.png)

[!TIP]

Active Citation Radio Selection: The Citations Checklist contains a single-select radio button column. Selecting a radio button activates that compliance citation and automatically deactivates all other citation records in the database.

---

Ingesting Data via CSV Imports

To support batch updates, the upload panel offers options to import compliance details.

• Selecting SKU Certificate Import locks the Processing Type dropdown to Replace and disables it, enforcing the strict 1-to-1 SKU-to-Certificate mapping on the backend.

---

What the Compliance Schema Contains

Field	Table	Validations & Requirements
SKU	SKUProduct	Required. Parent SKU code
AgencyProcessingCode	SKUProductCertificate	Required (e.g. REF, FGC, FCP). Max length 3
CertificateType	SKUProductCertificate	Required (GCC or CPC). Max length 10
ProductId	SKUProductCertificate	Required. Product ID or Globally Unique ID. Max length 100
CertifierId	SKUProductCertificate	Required if AgencyProcessingCode is REF. Max length 100
CPSCDisclaim	SKUProductCertificate	Optional (Y or blank). Max length 1
CPSCDisclaimReason	SKUProductCertificate	Conditional (required if Disclaim is Y). Max length 1
CitationCode	SKUProductCertificateCitation	Required (e.g. 16 CFR 1303). Max length 100
Active	SKUProductCertificateCitation	Required (bit flag). Indicates primary citation

---

CSV File Import Schemas

1. SKU CPSC Fields (sku-cpsc.csv)

Upserts CPSC compliance fields based on SKU:

SKU,CPSCDisclaim,CPSCDisclaimReason,CPSCIntendedUseCode,CPSCIntendedUseDescription,CPSCCommercialDescription,CPSCCommodityCharacteristicQualifier,CPSCCommodityCharacteristicDescription

2. SKU Certificate Import (sku-certificates.csv)

Links certificates, entities, and citations to SKUs:

SKU,AgencyProcessingCode,CertificateName,CertificateType,ProductIdQualifier,ProductId,CertifierId,BrandName,Model,ManufactureMonth,ManufactureYear,IdNumberType,IdNumber,DeclarationCode,ProductionStartDate,ProductionEndDate,LotNumberQualifier,InspectionStatus,InspectionDate,EffectiveDate,ExpiryDate,CitationCodes,CitationDescriptions,ManufacturerVendor,ManufacturerIdTypeCode,ManufacturerIdNumber,TestingLabVendor,TestingLabIdTypeCode,TestingLabIdNumber,CertifierVendor,CertifierIdTypeCode,CertifierIdNumber,Active,Notes

---

Supported Clearance Types

• T01 Entry (Consumption Entry)
• T11 Entry (Consumption Entry / Informal Entry)

Mandatory Deadline

• Compliance is mandatory beginning July 8, 2026 for all CPSC-regulated import entries.

---

*For technical questions or integration support, contact the Platform Engineering team.*

🆕 Montreal Facility

Release Date: June 8, 2026

What’s New

• Implementation for a new Client facility in Montreal, CA.
• Address is “2555 Dollard Ave, LaSalle, QC, H8N 3A9, CA”.
• Services using this facility include: Canada Post and UniUni.

How it works

- Accounts can use the Montreal facility if they have the Montreal terminal assigned which can be done through the account maintenance screen in the legacy portal as shown below:

- Users can have a "create shipment" request using service code “CPYUL” for Canada post service and then a label with the Montreal client facility address as shipper will be created like this label:

- Users can have a "create shipment" request using service code “uniuniyul” for UniUni service and then a label with the Montreal client facility address as shipper will be created like this label:

• Both service codes "CPYUL" and "uniuniyul" can be used in a "rateshipment" request.

🆕 CN22 Labels

---

CN22 Customs Declaration Form Support for Military Shipments

Release Date: May 25, 2026

---

What's New

The Legacy shipping API now supports automatic CN22 Customs Declaration Form generation for military shipments routed through supported carriers (FedEx, UPS). The CN22 form is required for shipments destined to APO/FPO/DPO military addresses and is now generated and returned alongside the shipping label in a single API response — no secondary request needed.

---

Why?

We've seen customer shipping rejects when a CN22 is not provided with the shipping label. USPS services automatically return a CN22 formatted label, whereas Fedex and UPS do not.

---

How It Works

The CN22 form format automatically matches the label format requested by the client. If a PDF shipping label was requested, the CN22 is returned as a PDF. If a ZPL label was requested, the CN22 is returned in ZPL format. No additional configuration is required.

The form is returned as a new field cn22_form in the existing shipment response:

<shipmentresponse tracknbr="61290397795820250031"
                  labelformat="ZPL"
                  label="..."
                  cn22_form="..."
                  carrier="FEDEX"
                  service="wizmofedexsmartpost"
                  url="https://www.fedex.com/fedextrack/?trknbr=61290397795820250031"/>

Clients who do not require CN22 forms will see no change to their existing API response.

---

Downloading the Form

The CN22 form is available directly from the shipment tracking page via the "Download CN22 Form" button, alongside the existing Get Label, Get Return Label, and Void Shipment actions.

---

CN22 Form — Sample Output

The generated form includes all mandatory customs declaration fields: shipper and recipient details, itemised contents with quantity, weight, declared value, HS code and country of origin per line item, package totals, the bilingual certification declaration, shipment date, and a barcode tied to the tracking number.

---

What the CN22 Form Contains

Field	Details
Shipper details	Name, address, country
Recipient details	Name, address, country
Contents description	Per line item
Quantity	Per line item
Weight (kg)	Per line item + total
Declared value (USD)	Per line item + total
HS Code	Per line item
Country of origin	Per line item
Certification declaration	English and French
Shipment date	Auto-populated
Barcode	Tied to tracking number

---

Supported Carriers

• FedEx
• UPS

Applicable Shipment Types

• Military addresses (APO / FPO / DPO)

---

*For questions or support, contact customer services or your account manager.*

---