The Customer Experience (CX) Engine: B2C and B2B Portals

The most visible component of the CoreForge ecosystem is the customer-facing web portal. This interface serves as the digital front door for hundreds of thousands of users, ranging from individual shoppers buying gifts to business owners importing commercial cargo. Our team prioritized User Experience (UX) design to maximize conversion rates and minimize support overhead

Seamless Registration and "Casillero" Generation

• The entry point for any user is the registration system. We engineered a frictionless sign-up flow that converts a visitor into an active user with a tangible asset: a personal U.S. shipping address.

  Algorithmic Address Assignment: Upon completing the registration form—which collects essential data such as name, email, and country—the system immediately executes a logic routine to generate a unique "Casillero" or Account Number. This number is not random; it is algorithmically linked to the physical warehouse operations in Miami (7801 NW 37 St. Doral, FL). This allows the warehouse sorting machines to instantly identify the owner of any incoming package based on the address label alone.

  Service Agreement Automation: To ensure legal compliance without slowing down the user, we automated the generation of Service Agreements. The system takes the data provided during registration, populates a legal template including the client's specific product or service tier, and generates a downloadable PDF service agreement. This feature demonstrates our ability to automate administrative tasks that typically create bottlenecks in client onboarding.

The Shipping Calculator and Cost Transparency

One of the primary friction points in cross-border e-commerce is cost uncertainty. Users hesitate to buy if they don't know the landed cost (shipping + duties + taxes). To solve this, we built a sophisticated International Shipping Calculator.

Multi-Variable Logic Engine: The calculator is not a static lookup table. It is a dynamic engine that processes multiple variables in real-time:

• Volumetric Weight Logic: The system calculates the greater of actual weight vs. volumetric weight (Length x Width x Height / Dim Factor) to ensure accurate carrier billing.
• Service Level Differentiation: It distinguishes between "Courier" (Express) and "Cargo" (Economy) rates, applying different pricing curves to each.
• Destination-Specific Logic: The engine integrates with a database of country-specific tax rules and customs duties, providing an estimated landed cost that includes import fees for countries like El Salvador or Guatemala.

The "Control Tower" Dashboard

Once a user is active, the Dashboard becomes their primary interface. We designed this view to provide total visibility, reducing the need for "Where is my order?" (WISMO) support tickets.

Real-Time State Mapping: The dashboard aggregates data from multiple sources. It pulls "Pre-Arrival" tracking data from carrier APIs (UPS, FedEx, USPS) and combines it with internal "Post-Arrival" data from the Miami warehouse. We implemented logic to guide the user: if a package hasn't reached Miami, the system explicitly advises the user to check the carrier's site, managing expectations proactively.

Invoice Upload and Pre-Alerting: To expedite customs clearance, we built a document management module linked to specific tracking numbers. Users can upload commercial invoices (images or PDFs) directly to the dashboard. The backend logic links this document to the package record, allowing customs brokers to prepare the declaration (Desaduanización) before the plane even lands. This "Pre-Alert" capability significantly reduces dwell time at customs.

Support and Self-Service Integration

Recognizing that logistics is a high-touch service industry, we integrated robust support mechanisms directly into the portal.

SmarterTrack Integration: Rather than building a helpdesk from scratch, we demonstrated our integration capabilities by connecting the portal to SmarterTrack. We implemented Single Sign-On (SSO) and data injection, so when a user clicks "Open Ticket," their account details are automatically passed to the support agent."

Knowledge Base and Community: We built sections for a Knowledge Base (FAQs) and a Community Forum, enabling peer-to-peer support and self-service resolution for common issues like "Restricted Products" or "Forgot Password.

The Operational Backend: Warehouse Management System (WMS)

While the frontend is about aesthetics and usability, the backend is about speed, accuracy, and logic. The Warehouse Management System (WMS) we built is the operational heart of CoreForge, enabling the processing of thousands of packages daily.

Inbound Processing and Barcode Logic

The efficiency of the Miami hub depends on how fast packages can be inducted. We implemented a high-speed scanning module.

Advanced Barcode Parsing: The system is programmed to recognize and parse multiple barcode formats. We implemented specific logic to handle custom barcode ranges, such as the "A-Series" and the newly introduced "B-Series". This allows the system to distinguish between different client types, consolidators, or service levels instantly upon scan. Client Lookup Tool: To prevent misrouting, we built a "Quick Lookup" tool for warehouse staff. By scanning a package label, the system instantly retrieves the Client Name, Account Status, and Service Level, displaying it on the workstation screen. This immediate feedback loop reduces errors at the point of entry.

Inventory Management and Containerization Once inside the warehouse, tracking individual packages becomes inefficient for transport. We introduced a "Containerization" or "Bagging" logic.

Bag ID Tracking Mechanism: We engineered a parent-child relationship model for shipments. Warehouse staff scan packages (Child IDs) into a physical bag or container. The system generates a unique Bag ID (Parent ID). The operational logic tracks the Bag, not the individual packages, during the airport-to-airport leg. When a Bag is scanned at the destination, the system recursively updates the status of all child packages contained within it. This logic reduces scanning requirements by orders of magnitude (e.g., one scan for 50 packages).

Storage Aging Logic: To manage warehouse capacity, the system tracks the "Days in Storage" for every item. We implemented business rules that trigger alerts or billing events when a package exceeds the "30 days free storage" threshold. This automated aging report helps the operations team clear out stagnant inventory.

Last-Mile Delivery and Dispatch Logic

The most complex phase of logistics is often the "Last Mile"—getting the package from the local hub to the customer. We built a sophisticated Dispatch Module to manage this.

City Filtering and Bulk Assignment: In many Latin American regions, geocoding can be imprecise. To solve this, we built a "City Filter" logic into the dispatch interface. Dispatchers can filter pending orders by City or Zone and perform a "Bulk Submit" to assign them to a specific branch or local hub. This ensures that packages destined for Santa Ana are not accidentally assigned to a rider in San Salvador.

Rider Assignment and Status Validation: We implemented strict validation logic to prevent operational errors. For instance, the system automatically checks the status of an order before allowing assignment. If an order is marked "Cancelled," the "Assign Rider" and "Branch Receive" options are programmatically hidden from the UI. This "State-Aware UI" prevents drivers from wasting fuel attempting to deliver cancelled orders.

Auto-Submit Workflow: To speed up the morning dispatch routine, we refined the UI logic. When a dispatcher selects a rider from the dropdown, the system triggers an "Auto-Submit," instantly assigning the orders without requiring a secondary confirmation click. These micro-optimizations save hours of labor over the course of a year.

Cargo and Freight Forwarding Logic

For commercial clients, the system switches modes from "Courier" to "Cargo".

Consolidation Logic: We built a "Consolidation Engine" that identifies multiple packages for the same user and groups them into a single shipment. This allows the system to calculate a "Volume Discount," applying a lower rate per pound as the total shipment weight increases. This logic encourages higher volume shipping and increases customer loyalty.

Multi-Modal Routing: The backend supports distinct workflows for "Air Cargo" (fast, expensive) and "Maritime Cargo" (slow, cheap). The system tracks these as separate pipelines, with specific milestones for "Port Departure" versus "Flight Departure," ensuring accurate tracking updates for each mode.

Financial Systems and Business Logic

A logistics platform is inextricably linked to financial transactions. Our team built a suite of financial modules to handle invoicing, payments, and compliance.

Dynamic Invoicing and Reconciliation

The system automates the generation of financial documents, reducing the workload on the accounting department.

Setoff and Reconciliation: We implemented a "Setoff Paid" status logic for invoices. This allows the finance team to mark invoices as settled against collected funds (e.g., prepaid credits or bulk payments), closing the loop on accounts receivable.

Pre-Alert Invoicing: The system is capable of generating invoices based on "Pre-Alert" data. If a user uploads their commercial invoice and the package dimensions are known (or estimated), the system can generate the shipping invoice before the package physically arrives, speeding up the payment and release cycle.

Cash on Delivery (COD) Management

In many target markets, Cash on Delivery remains a dominant payment method. We built a dedicated COD module to manage this risk-heavy process.

Multi-Business Management: We recognized that many of our clients are logistics aggregators or have multiple storefronts. We implemented a "Multiple Business Option" in the client profile. This allows a single login to manage COD remittances for multiple distinct business entities, selectable via a dropdown menu.

"Tomorrow Payable" Forecasting: To help finance teams manage cash flow, we built a predictive reporting tile called "Tomorrow Payable." This logic aggregates all COD deliveries marked as "Successful" today and calculates the total payout due to clients tomorrow. This real-time visibility prevents liquidity crunches.

Client Lifecycle Management

The system includes automated tools to manage the health of the customer database.

Auto-Deactivation of Dormant Accounts: To maintain database performance and security, we implemented a cron job (scheduled task) that scans for user inactivity. The logic identifies clients who have not placed an order in two months and automatically deactivates their accounts. This reduces the attack surface and keeps the active user database clean.

Churn Detection Reporting: We built a "Customer Inactivity Report" that runs daily. It identifies customers who were previously active but have not shipped in two weeks. This report generates a lead list for the sales team, enabling proactive retention outreach before the customer is lost to a competitor.