Published October 2026. Regulatory references are current as of September 2026.
Two things happened this month that raised questions most tracking systems cannot answer.
A tracking system tells you where a container is. That is useful, but it is not the same thing as visibility. Visibility is the ability to answer a question about your supply chain when someone asks it, and the questions being asked in 2026 are no longer about container position.
This article separates the three different things the industry calls visibility, explains why visibility projects so often disappoint after go-live, and sets out how Nissin’s EMG service is built to answer the harder questions rather than only the easy one, including why the platform underneath a service like it should be a decision rather than an assumption.
What follows describes general operating practice in supply chain visibility and outlines how Nissin’s EMG service is structured. It is not legal or regulatory advice.
What you’ll learn
- The three distinct things called visibility, and which one your problem actually needs
- Why visibility projects disappoint after the data starts flowing
- How a platform, a control tower and a managed operating layer differ
- Why the system a service runs on should be a choice rather than a condition
- Why round-the-clock exception coverage is a staffing question before it is a service question[NO1.1]
- What to ask for in a logistics RFP so the answers are comparable
Table of Contents
- The questions got harder this month
- Three different things called visibility
- Why visibility projects disappoint
- Platform, control tower, or managed layer
- How Nissin EMG is built
- Before you choose: a requirements checklist
- Frequently asked questions
- Summary
The Questions Got Harder This Month
Consider the two questions U.S. importers were handed in September.
The first is a timing question. Presidential Proclamation 11063, published on September 14, excludes certain Canadian products from importation “effective with respect to goods imported on or after 12:01 a.m. eastern time on September 29, 2026.” Note the trigger. Most tariff measures key to the date of entry. This one keys to the date of importation, and goods imported before that date but not yet entered stay under the earlier 50 percent duty instead.
So the operative question is not “what cleared customs?” It is “what did we import, on what date, and where is each of those shipments now?” A container-tracking view does not answer that. A purchase order linked to a shipment, an import date and an entry status does.
The second is a documentation question. On 2 September, CBP published an advance notice of proposed rulemaking, Heightened Import Disclosures for Supply Chain Visibility (91 FR 56408, docket USCBP-2026-1058, RIN 1685-AA47). Its summary is one sentence: “CBP is considering amending its regulations to give CBP greater visibility into the supply chains of goods imported into the United States.”
The notice, which implements Executive Order 14411 of 3 June 2026, sets out three proposal areas: foreign export documentation for imported goods; the parties involved in the manufacture, production, movement and exportation of imported goods; and innovative technical approaches for supply chain tracing. Among the documents under consideration are “Export Declarations made by the foreign exporter to the foreign customs authority.”
This is an advance notice, not a rule. Nothing is required of importers today, and comments are open until 1 December 2026. But the direction is clear, and the document at the center of it is one most U.S. importers have never held, because their supplier files it with a foreign authority. Whether it can be obtained is a conversation to open with suppliers and with your licensed customs broker now rather than later.
Both questions have the same shape. They are answerable only if order, supplier, document and shipment data are connected, and if someone is responsible for keeping that connection intact.
Three Different Things Called Visibility
Most disappointing visibility implementations start with a vocabulary problem. Three distinct capabilities share one word.
Shipment tracking
Where is this container, truck or air waybill right now? The data comes from carriers, and it is the most widely available and most commoditized of the three. It answers a location question and nothing else.
Order-level visibility
When will the items on this purchase order arrive, and what is the status of each one? This requires linking a PO and an item number to production progress, to a booking, and then to a shipment. Carrier data alone can never produce it, because the carrier does not know your PO number unless someone puts it there.
Inventory position
How much is where, including what is in transit and what is committed? This adds warehouse and inventory data to the layer above, and is usually what an executive means when they say the supply chain is not visible.
| Shipment tracking | Order-level visibility | Inventory position | |
|---|---|---|---|
| Answers | Where is it now | When will this PO arrive, and what state is each line in | How much is where, including in transit |
| Core data | Carrier events | PO, item master, production milestones, bookings, shipments | The above plus warehouse and inventory records |
| Who can produce it | Carriers, tracking tools | Forwarders, visibility platforms, managed services | Providers with warehouse integration |
| Typical failure | Data is there but tells you nothing actionable | PO and item linkage breaks at booking | Inventory and transit records disagree |
When a shipper says they cannot see their supply chain, they almost never mean the first column. Buying the first and expecting the second is the most common way these projects go wrong.
Not sure which of the three you actually need?
Tell us the questions you cannot answer today,
and we will map them to the data and the process that would answer them.
Why Visibility Projects Disappoint
Assume the right layer has been chosen. Four things still get underestimated.
The data problem nobody budgets for
Order-level visibility depends on the PO number and item number being present and correct at the moment of booking, every time, across every supplier. It also depends on your item master matching your supplier’s and your provider’s. Neither is a technology purchase. Both are ongoing operational discipline, and both are where the linkage silently breaks.
The freight outside your provider’s network
Very few shippers move everything with one provider. Whatever sits outside that provider’s own network has to be brought in by integration or by manual entry, and the answer to “how does your platform handle freight we do not tender to you” separates real multi-carrier capability from a demo.
The part that is not a technology problem at all
A dashboard that shows a red exception is not a resolution. Somebody has to see it, decide it matters, contact the right party, agree on an action and record what happened. Most visibility disappointment traces back to this: the data arrived, and the operating routine around it was never defined. There is a reason that part gets deferred. It is the only line in a visibility program with a recurring salary attached, and it competes with every other headcount request in the company.
The cost of that gap varies with the cargo. An exception on a temperature-controlled shipment has a much shorter fuse than one on dry freight, and in a capacity-constrained truckload market the recovery option you assumed you had may not exist.
What happens when the platform stops
This is no longer hypothetical. Cyber incidents have taken major logistics providers offline more than once in recent years, disrupting warehouse operations and order flow for the customers who depended on them. A provider’s cyber incident is your outage, and the question worth asking before signing is not only how the provider secures its systems, but whether a named team can run your orders and documents manually while systems are restored.
Platform, Control Tower, or Managed Layer
Three models are sold against the same problem, and they are not substitutes.
| Visibility software | Control tower program | Managed operating layer | |
|---|---|---|---|
| What you buy | A tool and a license | A standardized operating program | An operating team, governance and platform operation |
| Who runs it day to day | Your team | The provider, within a defined scope | The provider, configured to your process |
| Which system it runs on | The one you licensed | The provider’s own program platform | Whichever fits: yours, the provider’s or a third party’s |
| Hours covered | Your team’s working hours | The program’s defined hours | Configured to the operation, up to 24/7 |
| Best fit | Shippers with internal resource to operate it | High volume, standardized flows | Mid-sized operations without spare headcount |
| Who handles exceptions | You | The provider, per playbook | A dedicated team that knows your account |
| Adaptation | Configuration within the product | Limited; you adapt to the model | Configured around your structure |
Software is the cheapest to buy and the most expensive to operate, because operating it is your job. A control tower program suits volume and standardization, and the trade-off is that you adapt to the model. The third option is the least well defined in the market, which is why it is worth being specific about what it contains. It is also the only one of the three that does not require you to adopt a particular system, and that matters more than it sounds: platforms get replaced, and the operating routine should outlive the change.
How Nissin EMG Is Built
EMG stands for End to End Management Group. It is a coordinated management layer that sits between your team and your supply chain partners, and the service guide states its intent plainly: EMG is “not a replacement for existing teams, but an extension of them.”
Four modules, configured rather than packaged
EMG is not a single product with a feature list. It combines four service modules according to each customer’s supply chain structure, operating requirements and reporting needs.
| Module | What it covers |
|---|---|
| Order Collaboration | PO lifecycle, supplier follow-up, production milestones, shipment readiness |
| Transportation Management | Booking coordination, carrier alignment, routing, execution control |
| Exception Management | Risk detection, escalation, resolution tracking, corrective actions |
| Visibility and Reporting | Centralized data, KPI reporting, dashboards, operational insights |
The operating model
The modules run inside a five-step cycle. Plan defines scope, stakeholders, milestones and reporting needs. Execute coordinates suppliers, bookings, documents and logistics partners. Monitor tracks orders, shipments, milestones and KPI signals. Resolve escalates exceptions, documents decisions and follows up on corrective actions. Improve reviews performance, root causes and optimization opportunities.
The governance layer
This addresses the failure mode described earlier. Before the data starts flowing, EMG defines a customer-specific governance layer covering service scope, meeting cadence, escalation workflow, KPI framework, issue tracking and reporting format. In other words: who looks at what, how often, what counts as an exception, who it goes to, and how the answer is recorded.
A dashboard without that definition produces reports. A dashboard with it produces decisions.
The platform layer, and why Nissin stays neutral about it
Every EMG engagement runs on a transportation management or visibility platform. Which one is a decision, not a default.
Nissin works as a platform-agnostic operator. Where a customer has already licensed a system, EMG runs inside it. Where there is none, Nissin advises on selection and implements what fits the lanes, the supplier base and the reporting the operation needs. The service is not tied to one vendor, and it does not ask a customer to abandon a system they have already paid for. What matters is the capability set rather than the name on the login screen, and the checklist further down this article is written to test exactly that.
Two capabilities deserve a note whatever the platform. Predictive ETA identifies issues before they become delays, but it is a forecast rather than a commitment, and it is worth agreeing with any provider on which milestone is being predicted. Performance management across suppliers, carriers and logistics providers is what turns a year of exception records into a procurement conversation, which is where visibility finally pays for itself.
Neutrality has a practical payoff. Licenses lapse, vendors get acquired, and systems are replaced on a schedule the shipper rarely controls. When the operating routine lives inside the platform, that change is a project. When it lives in a governance definition and a team that knows the account, it is a migration. Behind all of it sits a dedicated operations team assigned to the account, working to documented processes. People, process and platform together are what the service guide means by a management layer, and only one of the three is interchangeable.
Coverage, and what it costs to staff
Exceptions do not keep business hours. A booking that fails in Shanghai, a customs query in Rotterdam and a missed pickup in Long Beach land at different points in the same 24 hours, and the window for acting on each is measured in hours.
Covering that from one office means either letting overnight events wait until morning, or hiring for shifts. Most shippers quietly choose the first and then describe the result as a visibility problem.
EMG is staffed so that the second option does not require a hiring plan. Coverage is set to the operation: business hours in one time zone, extended hours across two, or continuous cover where the lanes and the cargo justify it. Nissin runs 24/7 operations where a customer needs them.
The service guide lists lower cost operations and scalable support among the benefits of EMG, and this is where both come from. What you are buying is not only the monitoring. It is the ability to change how many hours of it you get without changing your own org chart.
Before You Choose: A Requirements Checklist
Put these in the RFP, and the answers become comparable.
- Which of the three layers is in scope: tracking, order-level, or inventory position
- Whether PO number and item number are captured at booking, by whom, and what happens when they are missing
- How freight moved by providers outside the scope is brought into the same view
- Which platforms the provider can operate on, whether a system you already license can be used, and what moves with you if it changes
- Which milestones are predicted, and against what baseline
- Who monitors exceptions, during which hours, and in which time zone, and what extending those hours would cost[NO5.1]
- The escalation path by exception type, with a target response time for each
- The KPI set, the reporting format and the review cadence
- Data ownership, retention, and what you receive if the relationship ends
- Incident notification timelines, and the manual fallback procedure if provider systems are unavailable
- Which regulatory data the provider can produce on request, and in what format
Frequently Asked Questions
What is the difference between shipment tracking and supply chain visibility?
Shipment tracking answers where a container, truck or air waybill is right now, using carrier event data. Supply chain visibility is broader: it connects purchase orders, suppliers, production milestones, shipments and often inventory, so you can answer questions about orders and stock rather than only locations. Tracking is a component of visibility, not a synonym for it.
What is order-level visibility?
It is the ability to see the status of a purchase order and its line items across production and transportation, rather than only the container they eventually travel in. It requires the PO number and item number to be linked to the booking and carried through the shipment record. Carrier data alone cannot produce it, because carriers do not hold your order data.
Do I need a visibility platform or a managed service?
It depends on whether you have people to operate it. A platform gives you data and leaves the monitoring, escalation and follow-up to your team. A managed service provides the operating routine as well, including who watches for exceptions and what happens when one appears. If your constraint is headcount rather than software, a platform alone will underdeliver.
Does a managed visibility service lock me into one platform?
It should not. Ask any provider whether the service can run on a system you already license, what happens if you change platforms mid-contract, and who holds the configuration and the historical data when you do. A provider whose operating model only works inside one vendor’s product is selling you that vendor as much as the service. Nissin’s EMG is platform-agnostic and can operate on a customer’s existing system.
Can a managed logistics service monitor shipments outside our business hours?
Yes, and for many shippers it is the main reason to use one. Exceptions on international freight occur across every time zone, while most in-house teams cover one. A managed service can be set to business hours, extended hours or continuous coverage, and Nissin’s EMG runs 24/7 operations where a customer’s lanes require it. The question worth asking a provider is not whether they can do it, but what changes in price and in process when the hours change.
What is a predictive ETA and what are its limits?
A predictive ETA forecasts arrival from current transport data and historical patterns, flagging problems before they become delays. It is a forecast, not a commitment, and its value depends on which milestone it predicts. Agree with your provider on whether it forecasts vessel arrival, port availability or final delivery, because those are different numbers.
What should a logistics RFP ask about visibility?
Ask which layer is in scope, how PO and item data is captured at booking, how freight outside the provider’s network is included, which milestones are predicted, who monitors exceptions and when, the escalation path and response times by exception type, the KPI and reporting cadence, data ownership on exit, and the manual fallback if systems are unavailable.
Summary
- Tracking, order-level visibility and inventory position are three different capabilities. Buying one and expecting another is the most common reason these projects disappoint.
- The questions being asked of importers are moving toward order, document and date-level answers, as September’s Canada prohibition and CBP’s disclosure notice both show.
- The hard part is rarely the technology. It is the data discipline at booking and the operating routine after the dashboard lights up.
- Ask any provider how freight outside their network appears in the view, and what happens to your operation if their systems go down.
- The operating routine is usually the missing piece because it is the only part with a salary attached. Buying it as a service adds coverage hours without adding headcount.
- EMG combines four configurable modules, a five-step operating cycle, a customer-specific governance layer and a dedicated team assigned to the account, operating on whichever platform fits the customer rather than a single fixed system.
Visibility projects rarely fail because the technology does not work. They fail because nobody defined who looks at what, when, and what happens next. EMG starts with that definition and builds the operating routine around it, on whichever platform the account calls for. If you can tell us the questions your supply chain cannot currently answer, we can show you what it would take to answer them, and how many hours of the day that coverage needs to run.
Disclaimer
Regulatory references in this article are current as of September 2026. The CBP advance notice of proposed rulemaking discussed here is a request for comment, not a rule, and creates no obligation on importers at this time; the comment period closes 1 December 2026. Import prohibitions and tariff measures change frequently and should be confirmed against the Federal Register and CBP guidance before any operational decision.
Nissin International Transport U.S.A., Inc. is a freight forwarder and licensed U.S. customs broker. EMG service scope, modules and reporting are configured per customer and agreed in the service definition; nothing in this article is a commitment to a specific scope, service level or system capability. Platform capabilities differ by system and by customer configuration, and are confirmed per engagement. Nothing here is legal or regulatory advice.
References
- U.S. Customs and Border Protection. Heightened Import Disclosures for Supply Chain Visibility, advance notice of proposed rulemaking, 91 FR 56408, 2 September 2026. https://www.federalregister.gov/documents/2026/09/02/2026-17926/heightened-import-disclosures-for-supply-chain-visibility
- Proclamation 11063 of 8 September 2026, Excluding Certain Canadian Products From Importation Into the United States, 91 FR 58325, published 14 September 2026. https://www.federalregister.gov/documents/2026/09/14/2026-18837/excluding-certain-canadian-products-from-importation-into-the-united-states-in-response-to-continued
- Nissin International Transport U.S.A., Inc. NIT EMG Service Guide, September 2026.
