Modules

Active Lambda modules and the shared services behind them.

Lambda is organized as entitled modules plus shared platform services. Modules are what your organization turns on. Platform services accept CargoWise traffic, deliver artifacts, and notify people — they are not separate products.

Active modules

Stamping

CargoWise accounting documents → fiscal checks → Facturapi CFDI → artifacts back to CargoWise.

Analytics

Org-scoped reporting Postgres for SQL, Power BI, and curated views.

Stamping

The core product. Income invoices, payment complements (REPs), credits, and cancellations enter through Lambda ingress, reconcile against SAT rules, stamp when eligible, and return XML/PDF to CargoWise when outbound is configured.

You work this module from the invoice workspace: statuses, notes, timelines, and the next safe action when Lambda offers one. Recovery lives inside stamping — it is not a separate module.

Start with Stamping overview and How stamping works.

Analytics

Long-term reporting storage for your organization. You get a read-only Postgres login scoped to your org, a stable reporting schema, curated business tables, and credentials you create in Lambda.

Analytics does not store invoices, Facturapi responses, or SAT artifacts. Stamping owns fiscal evidence; Analytics owns reporting visibility.

Analytics uses its own CargoWise outbound target. Stamping ingress traffic does not fill Analytics.

Start with Analytics overview and Connect.

Shared platform services

These surfaces are always part of Lambda. They support the modules above rather than replacing them.

Service	What it is	Where you see it
Lambda ingress / CargoWise events	Front door for CargoWise eAdaptor outbound XML into stamping (and related module routing). Every request is captured for the event list.	Sidebar Ingress — searchable event list
Lambda outbound	Post-stamp delivery of XML/PDF (and cancellation receipts) to CargoWise inbound. Separate from stamp success.	Settings → CargoWise
Notifications	In-app feed (and email prefs) for failures, system errors, stamp credits, and approval needs.	Sidebar Notifications

Analytics deliveries use a separate CargoWise outbound URL — not the stamping ingress front door.

Ingress is acceptance, not completion

When CargoWise pushes a document to stamping ingress, Lambda returns acceptance after the capture is saved and work is queued. CargoWise treats that as delivered. The stamp may still be Received or Processing in the invoice workspace — check there if a document seems stuck.

Outbound is separate from stamped

A CFDI can be issued while CargoWise delivery is still retrying. Stamp success and outbound delivery are different outcomes.

Workspace map

Sidebar	Role
Notifications	Alerts for your organization
Ingress	CargoWise events and captures
Stamping	Invoice workspace (when the module is enabled)
Analytics	Connection kit and reporting contract (when enabled)

Settings → CargoWise configures enterprise/server IDs, ingress auth, and outbound. Settings → Stamping / Analytics hold each module’s credentials and options.

Next

• AI-native — how assistants participate inside these modules
• Stamping overview — CFDI path and workspace statuses
• Analytics overview — reporting Postgres