Mercor’s public data program names tools and operating-record examples across several industries. Use that evidence to frame a collection question, then make your own inventory specific. A shipping manifest, a dispatch log and an invoice are three record groups. They become a connected delivery collection only when the references and available history support that description.
The supported interest
Mercor names Slack, Teams, Gmail, Outlook, Drive and Salesforce among its tools. Its industry examples include shipping manifests, dispatch logs and invoices; order records and inventory logs; and client decks, statements of work and project files.
Sources: Mercor
Describe the operational event at the center
For a fictional delivery operation, shipment S-812 is the central event. A dispatch row schedules it, a manifest lists its contents, an exception message records a delay and an invoice records the billed service. Inventory each group with its own dates, format and reference fields.
The manifest number and shipment number may not be the same. Preserve both and identify the table or explicit reference connecting them. A customer account can have many shipments on one day; matching on customer and date alone may produce the wrong link.
| Fictional group | Own identifier | Relationship to check |
|---|---|---|
| Shipment | Shipment S-812 | Central unit of work |
| Manifest | Manifest M-49 | Shipment reference |
| Dispatch event | Event D-73 | Shipment reference and sequence time |
| Exception message | Thread E-61 | Explicit shipment or manifest reference |
| Invoice | Invoice I-220 | Shipment lines or supporting schedule |
Give exceptions their own inventory row
Do not collapse a late delivery, replacement dispatch and credit into a final delivered status. If the event records survive, name them. If they are represented only in free-text notes, describe that format. If the operational explanation was given by phone and never recorded, leave it outside the collection.
This distinction can change the question you ask without requiring a claim about extra value. A collection of final delivery rows and a collection of linked exception events are different scope proposals. Either can be described accurately.
Keep the source level visible
A named invoice or dispatch-log example supports a more specific interest connection than an industry heading alone. Ask about the record types and software formats in your export.
- Name the operational unit and its persistent reference.
- Record how multi-stop or split shipments are represented.
- Separate the event time from the time a row was entered.
- Identify where the final resolution is documented.
- List groups whose links remain unverified.
Prepare the scope question
An effective question is whether the proposed linked shipment, dispatch and invoice groups fit the current opportunity, and whether the provider needs exceptions, attachments or a particular date span clarified. Keep payment questions with the actual proposal rather than deriving a price from the number of groups.
Questions about this comparison
Can we label all logistics records an exact match?
No. Use the specific named record interests where supported. Other collections may have only an industry connection or remain unresearched.
What if shipment IDs changed after a migration?
Keep old and new identifiers separate and record whether a cross-reference survives. Do not invent a matching table.
Should duplicate dispatch attempts be removed?
Describe the attempts and their event identities first. A repeated attempt may be part of the workflow rather than a duplicate file.
Sources
- Mercor program pageMercor · Checked 2026-10-06