For mid-market and enterprise
Already importing? Make the next decision with better evidence.
How an established import team can evaluate landed-cost analysis, duty review and pre-entry preparation without assuming it must replace its existing broker.
General information, not a duty quotation. Shipment-specific conclusions require licensed customs broker review.
An established import program still has decisions to make.
A new supplier, revised product, changing margin target or regulatory change can reopen assumptions in a mature import program. Greenwich’s value proposition is not limited to obtaining an importer number. It connects landed-cost scenarios, accountable broker judgment and pre-entry readiness.
If you already have a broker, start by defining the problem and the handoff. Do not assume Greenwich has a technical connection, mandate or data-sharing agreement with that broker. Compatibility and responsibilities must be agreed for the specific engagement.
Use a proposed responsibility matrix to start the conversation.
This is an engagement-planning checklist, not a promise that every role or integration is available in every engagement. The actual parties and responsibilities must be confirmed before work begins.
| Work item | Proposed responsibility to confirm | Required handoff |
|---|---|---|
| Product and commercial facts | Customer supplies and confirms the underlying facts | Specification, transaction details and production evidence. |
| Scenario analysis | Greenwich scope agreed with the customer | Inputs, assumptions, exclusions and comparison outputs. |
| Customs judgment | Named licensed broker within agreed scope | Supported classification, origin and valuation decisions. |
| Entry submission | Authorized filing broker | Approved instructions, complete documents and required authority. |
| Inventory and purchase decisions | Customer’s commercial and planning teams | Reviewed scenarios and unresolved risks, not automatic purchasing instructions. |
| Exceptions and changes | Named owners on each side | Escalation, version control and approval points. |
Agree a limited first deliverable.
Choose one product family or supply lane and one decision. Review a representative shipment or entry rather than assuming a full data migration. Agree which data can be shared, who can see it and which output the filing broker can use.
Describe the deliverable plainly: for example, a reviewed assumptions table, cost comparison or document-gap list. File format, transfer method, system compatibility and implementation timing need confirmation; an export is not the same as a live integration.
Keep judgment and liability clear.
Analysis does not transfer the importer’s obligations, and broker involvement is not a guarantee of clearance. The objective is to make the facts, review decisions and exceptions visible to the responsible people.
Questions, answered directly.
Do we have to replace our broker?
Not a decision to assume at the outset. Discuss the scope and confirm whether a workable collaboration and handoff can be agreed with the parties involved.
Does Greenwich connect automatically to our broker or ERP?
Do not assume so. Confirm supported files, transfer methods, permissions and any specifically configured connection during the evaluation.
Sources and limits
Sources support the stated context, not an endorsement of Greenwich or a shipment-specific determination.
Define your next U.S. decision.
Agree the question, evidence and responsibilities before acting.
Import readiness review