APEX Load Entry: Record Details, Receipt Lookup, and Unconfirmed Workflow

Overview

APEX Load Entry appears to refer to load information handled within Capstone Logistics’ broader APEX warehouse technology environment. The available sources show what one completed load-related record contains and how to search for an unloading receipt, but they do not document the full process for opening, completing, or submitting an entry.

These are three related but distinct concepts. The APEX Technology Suite is Capstone’s warehouse operations and reporting platform. It collects operational data, supports transaction automation, and connects with visibility and predictive analytics tools.

An APEX load record is an individual operational artifact associated with a particular load. The supplied example identifies a receipt, location, work date, carrier, dock, door, purchase order, vendor, pallet count, amount, and signature. It demonstrates one completed record structure; it does not establish a universal form or required-field specification.

An unloading receipt is the downstream document a driver, carrier representative, or operations user may need after unloading. Capstone provides an official driver route for requesting these receipts and a separate search page that references PO number, work date, and total cost.

What an APEX load record can show

A completed APEX load-related record can combine identification, facility, carrier, handling, commercial, and acknowledgment details. The supplied record preview provides one concrete example of a completed record. It should be treated as a recognition aid, not proof that every entry contains the same fields.

In that example, the visible details are:

• Receipt number: 97fd13a4-787c-4411-9fcb-57597d567265, which identifies the displayed receipt.
• Location and work date: SPARTANNASH LIMA OH and 2023-12-12, connecting the record to a facility and processing date.
• Bill code and carrier: RCOD30467 and LANDSTAR, providing billing-related and transportation identifiers.
• Dock and door: DRY and 2, indicating the operational dock designation and door shown on this record.
• Purchase order and vendor: 541289 and HARVEST HILL, linking the load to the displayed purchasing and vendor information.
• Load quantity, amount, and signature: 17 total initial pallets, $162.50, and the signature name Richard Derosia.

A practical review starts by matching the record against information already associated with the load. For example, a user holding PO number 541289 could compare it with the record’s work date, carrier, facility, pallet count, and displayed amount. Agreement across several fields provides more context than relying on the PO number alone.

The numbers should not be extended beyond what the record says. Although the example displays an initial-pallet count and an amount, it does not label the amount as a pallet rate or provide a charge formula. Dividing the amount by the pallet count would produce a mathematical result, but the source does not establish that such a calculation represents Capstone’s billing method.

The same caution applies to labels such as bill code, dock, and door. The preview confirms that these labels appear in this example; it does not define their validation rules, acceptable values, or whether users must enter them manually.

How to find an unloading receipt

Capstone’s supported public route begins with its Driver Information & Portal page, which includes a “Request Unloading Receipts” option for searching for a warehousing receipt. That link leads users toward Capstone’s external receipt-search service.

The Capstone receipt-search page states that users can find load receipts using three pieces of information:

• PO number
• Work date
• Total cost

Before searching, copy these values exactly from the load paperwork or completed record available to you. In the supplied example, the corresponding visible values are PO number 541289, work date 2023-12-12, and amount $162.50. These values illustrate how the documented search inputs may correspond to a completed record, but they belong to that single example and should not be used for another load.

The receipt-search excerpt also displays “Sign In / Register.” It does not explain whether authentication is required for every search, which users should register, or what credentials are accepted. Follow the prompts presented on the official page rather than assuming that credentials for another Capstone service will work.

The available evidence ends at the search inputs. It does not document the exact sequence after a search is submitted, including how results are matched, whether multiple records can appear, or how a receipt is viewed, downloaded, or printed. It also does not prove that the driver portal, receipt-search service, or CapstonePay is the APEX Load Entry interface. These routes should be understood as supported receipt and driver services, not as confirmed entry screens.

What APEX tracks beyond one load record

A load record is one operational artifact, while APEX has a broader reporting role. Capstone describes APEX as a proprietary warehouse technology solution that captures and interprets operational data and integrates with visibility and predictive analytics tools and applications.

Its documented measurements include driver gate-in and gate-out times, load and unload times, detention tracking, temperature recording, on-time pickups, and driver-experience feedback. APEX also reports pricing measures such as price per load, price per pallet, and price per case. Other listed measures include pallets and cases per hour, receiving violations, on-time deliveries, average lead time, and cargo-loss percentage.

These measurements explain why consistent load information can matter beyond retrieving one receipt. A facility may use operational data to examine timing, dock status, carrier or vendor performance, temperature information, productivity, and pricing at different levels. Capstone says its reporting can analyze periods including a day, week, month, quarter, or year and can examine site, regional, or corporate levels.

That broader reporting context does not mean every metric appears on an individual APEX load record. The supplied record preview shows fields such as carrier, dock, door, vendor, pallets, and amount, but it does not display the complete set of platform metrics. We should therefore distinguish between data visible on one record and measures that the wider APEX suite can report.

Limits of the available APEX Load Entry guidance

The available sources support a bounded explanation: Capstone’s APEX suite handles warehouse data and reporting, one supplied record shows recognizable load details, and the official driver route supports unloading-receipt lookup. They do not provide a complete APEX Load Entry operating manual.

In particular, the sources do not document the full workflow from initial access through entry creation, validation, submission, approval, correction, and payment. A public receipt route cannot fill those gaps because searching for a completed receipt is a different task from creating or approving the underlying load entry.

Access, permissions, and submission steps

The evidence does not identify the exact application or authenticated portal used to open APEX Load Entry. A separate public result labeled “Apex Site Administration” establishes only that a page with that title exists; it does not establish that drivers, carriers, receiving staff, or load administrators should use it for Load Entry.

No supplied source defines eligible user roles or explains who can create, edit, validate, submit, or approve an entry. The sources also do not document a login sequence, account-creation process, site-selection step, or method for associating an entry with a particular warehouse.

Submission instructions are similarly absent. There is no supported sequence for starting a new entry, saving an incomplete record, attaching images, confirming pallet or PO data, submitting the entry, or verifying acceptance. Capstone’s APEX overview says the broader platform manages image uploads and automates transactions, but that platform-level description is not a field-by-field Load Entry procedure.

Required fields, errors, and corrections

The fields visible in the completed example should not be treated as a required-input checklist. The preview demonstrates that one record contains a receipt number, location, work date, bill code, carrier, dock, door, purchase order, vendor, initial pallet count, amount, and signature. It does not label those fields as required or optional.

The source also does not define how each value should be formatted. It provides no documented rules for dates, PO numbers, bill codes, carrier names, pallet quantities, signatures, or amounts. There is no evidence showing validation messages, duplicate-entry warnings, rejected values, or the conditions under which an entry can proceed.

Correction procedures are also unresolved. The available material does not say whether a submitted record can be reopened, which role may edit it, whether changes require approval, or how a user should address an incorrect carrier, PO, pallet count, date, or amount. Those questions require official workflow guidance tied to the user’s role and facility.

Charges and payment timing

The evidence shows pricing information at two different levels, but it does not explain the transaction rules. Capstone’s APEX overview lists price per load, price per pallet, and price per case among the platform’s reported measures. The completed example separately displays an amount of $162.50 alongside 17 initial pallets.

Neither source provides the formula behind that amount. The record does not identify a base fee, rate, surcharge, tax, adjustment, or other component, and it does not state that multiplying or dividing by the pallet count reproduces the charge. The broader list of pricing metrics cannot be used to infer which measure governed this particular record.

The sources also do not establish when payment is due, whether payment must occur before a receipt becomes available, or how CapstonePay relates to a specific unloading charge. No supplied material documents a dispute, refund, adjustment, or billing-correction process. A displayed total can therefore be used as a receipt-search input or record-matching value, but not as evidence of how the charge was calculated, paid, or approved.