Use creation-origin fields to distinguish imports from manual lookups

Provider metadata identifies where load details came from; it does not necessarily identify what created the record. A dashboard lookup can save the same provider marker used by an automatic poller. Before attributing creation to a webhook or poller, inspect the explicit creation-origin field, creating-user evidence, and timestamps. Use provider fields for source-data attribution and creation-origin fields for workflow attribution. This distinction matters when checking whether automation replaced a manual action. It does not prove the precise UI action without an audit event.

Applies when: manual and automatic ingestion paths share provider normalization and raw-data formats. Keywords: TMS provider metadata dashboard poller webhook creation origin attribution