For mid-market and enterprise
Evaluate Greenwich for your U.S. import program
A practical evaluation checklist for European mid-market and enterprise teams: commercial scope, evidence, broker responsibilities and data-handling questions.
General information, not a duty quotation. Shipment-specific conclusions require licensed customs broker review.
Begin with the decision and the evidence.
Choose a bounded commercial question: a sourcing comparison, a product-family review, an import-readiness issue or a response to changing trade rules. Bring available specifications, quotes, commercial documents and representative entries where relevant. Do not send a full confidential dataset before agreeing sharing arrangements.
Greenwich’s approved positioning combines Enterprise AI and accountable customs brokers for landed-cost scenarios, duty opportunities and shipment readiness. This checklist helps establish the particular service scope. It is not a contract, service-level commitment or security certification.
Five things to establish before an engagement.
| Evaluation topic | Evidence or answer to request |
|---|---|
| Commercial scope | Products, origins to evaluate, transaction structure, decisions and exclusions. |
| Inputs and output formats | Supported file types, document quality, required fields and the deliverables the team can use. |
| Broker responsibilities | Named participants, authority, judgment, filing and escalation responsibilities. |
| Implementation | A bounded sample, milestones, dependencies and an agreed success measure. |
| Data governance | Contractual permissions, access, hosting, retention, deletion and security review for the proposed scope. |
Files and exports are not the same as integrations.
A PO, supplier quote, specification or system export can help frame the commercial question. Confirm the actual supported ingestion route before assuming any particular file type or connector works in your engagement. A screen demonstration does not establish a live ERP or TMS integration.
The existing public import-desk preview demonstrates an invoice-to-classification workflow with sample information. The worked comparison linked below is a static educational model, not a claim that a particular multi-system workflow is already deployed.
Security and legal review should get real answers.
Request the current, scope-specific data-processing and security information during evaluation. Confirm access controls, subprocessors, storage locations, retention, deletion and incident contacts with the responsible owner. No SOC 2, ISO 27001, EU-only hosting or data-residency certification is asserted by this page.
Do not assume that a statement about software capabilities changes the importer’s duties or the broker’s authorization. Responsibilities, supported workflows and implementation dates should be documented in the engagement.
Agree what a successful evaluation means.
Use observable outputs: a comparison with traceable assumptions, a reviewed unresolved-questions list or more complete pre-entry data. Distinguish a useful analysis from a realized duty saving, and an evaluation from a production rollout.
Questions, answered directly.
Can you promise a same-week enterprise deployment?
No universal timeline is stated here. Scope, data quality, permissions, review needs and any required connections must be established before a deployment plan can be agreed.
Are the scenario tables live software output?
No. The public worked scenario is explicitly illustrative. Evaluate actual supported workflows and outputs with the responsible Greenwich team.
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