MSPO Trace FAQ
How to use this independent public-data tool and interpret its entities, identifiers, status labels and map locations without treating the site as an official register.
Data source and snapshot
MSPO Trace derives its public entity dataset from the official source named below. The local record count is read from the dataset metadata, not hard-coded into this page.
- Exact public source
- Official MSPO public data
- Records in derived snapshot
- Not loaded
If snapshot metadata cannot be loaded, no count is estimated. Use official MSPO channels for a current source check.
Questions and answers
The answers below describe how MSPO Trace presents its derived dataset; they do not interpret the legal effect of a source record.
What is MSPO Trace, and is it an official MSPO service?
MSPO Trace is an independent discovery and visualisation layer derived from official MSPO public certification data. It helps users find and compare public entity records; it is not an official MSPO service and is not operated by the MSPO scheme, MPOCC, MPOB or a government body. For official scheme information and current verification, use official MSPO channels or the relevant certification body.
Where does the data come from, and how current is it?
The source is official MSPO public certification data. The data source panel reads the derived snapshot's record count from /data/entities-v2.json metadata. MSPO Trace does not publish a synchronisation time, so records here should not be treated as current; verify time-sensitive information through official MSPO channels or with the relevant certification body.
How do the entity, UUID, entity code, Track ID, MPOB number, company and parent fields differ?
An entity is the source-listed physical site, facility or grouped operating unit represented by a row. The entity UUID is the source's technical identifier for that row; it is not a certificate or licence number. The entity code is the source's code for the entity and should not be assumed globally unique. A Track ID is a certification grouping or reference and may be shared by several entities. The MPOB number is a source-reported MPOB reference field, not proof of current licensing. Company and parent are organisation names associated with the row and are useful for discovery or grouping, not a substitute for official corporate or ownership records.
Why can one Track ID appear on several entities?
One Track ID can cover multiple source-listed entities under the same certification grouping. MSPO Trace keeps the physical sites, facilities or grouped operating units as separate entity records instead of collapsing them into one certificate row, so a repeated Track ID is not necessarily a duplicate.
How should I read the status labels?
The default Current view includes source records labelled ACTIVE, REINSTATE, EXTENDED or TRANSFERRED. DELAYED and SUSPENDED records are available separately through status or attention views and filters. These are source labels and MSPO Trace does not decide certificate validity, legal or licence effect, or trade acceptability. Verify a time-sensitive record through official MSPO channels and with the relevant certification body.
How accurate are the locations on the Entity Map?
Map pins retain the validated precision published by the source so they use the most accurate source points available. A pin is still a source-reported reference point, not a surveyed legal boundary or proof of an exact entrance, parcel or operating footprint. Records with missing, invalid or out-of-range coordinates are omitted from the map but remain available in the list and search views.
How should I use search and the Entity Map?
Use Search All Entities when you want a text-based list and category, state or status filters. Use the Entity Map to explore the source-reported locations geographically, then consult the corresponding list record and official MSPO channels for identifiers and current source details. Clear filters and try a shorter term if an initial search returns nothing.
Why might a record be absent?
A record may be outside the current public source snapshot, recorded under another entity, company or parent name, excluded by an active status or category filter, or not yet included in the latest MSPO Trace refresh. A listed record can also be absent from the map when its coordinates are unusable. Absence from MSPO Trace is not a finding about certification or licence status.
How do I request a correction?
Submit the correction through official MSPO channels or to the relevant certification body shown with the record. MSPO Trace does not originate or authoritatively amend official source data. After the public source is corrected, a later MSPO Trace refresh can carry the revised value into its derived dataset; urgent decisions should be checked directly with the official source.
Does MSPO Trace publish contact data or function as a licence register?
MSPO Trace does not publish email addresses taken from source workbooks in its public entity dataset. It is also not a statutory licence register: a displayed MPOB number is a source-provided reference and does not establish a current licence or any legal effect. Use the relevant official authority and source record for licensing or statutory checks.