Documents sent for Israel customs clearance: how to follow up

The community question

A public Facebook question describes a first shipment held at Ben Gurion while documents were requested. The author had sent documents and was unsure how to follow up without a reply, later reporting release after email exchanges. That account does not establish which step caused release or a standard response time. This guide turns the question into a document follow-up record.

Verify the request and the responsible contact

Start from a carrier or clearance contact you have independently verified using the provider’s official website or an existing shipment agreement. Match the airway bill, tracking number or clearance reference to your shipment. Ask which team issued the request and where the complete request can be viewed. If a message unexpectedly asks for identity or payment information, verify it before opening its link or sending files. Record the contact channel and case number. A familiar logo or an email subject containing a tracking number is not enough to authenticate the sender.

Turn the request into specific open items

Keep the request’s exact wording and date, then separate it into individual items. Ask whether the issue concerns a missing file, an unreadable copy, inconsistent invoice data or a product-specific question. Describe the goods by model, material, intended use and actual quantity when relevant. Identify who must supply the answer: seller, manufacturer, importer or clearance provider. Do not substitute a generic certificate for a document requested for a particular model. FedEx Israel describes contacting recipients when import information is missing or incorrect; the requirements for your shipment still need confirmation from its responsible handler.

Match each answer to one file version

Create one row per requested item with the shipment reference, document name, issuer, version date and responsible person. Check that invoice, packing information and product descriptions refer to the same goods and quantities. Where an order travels in several parcels, identify which parcel each document covers. Preserve the original file and label a correction clearly; ask the issuer to correct its own document rather than quietly changing it yourself. In the covering message, explain which requested item each attachment answers and list anything still pending. This makes a partial submission distinguishable from a complete response.

Use the confirmed submission channel

Ask the handler to confirm the official portal or email address, accepted file formats and any size limits. Use the reference they specify so the files reach the correct case. Retain the submission timestamp, attachment list and confirmation screen or sent-message record. If the channel reports an upload failure, resolve it rather than relying on the attempt. Send sensitive documents only through the verified channel to the party that needs them; this article and its downloadable worksheet do not request uploads. When someone else submits on your behalf, obtain their submission reference and exact file versions.

Separate sending, receipt, acceptance and release

Use separate fields in your own record for sent, receipt acknowledged, accepted for the requested purpose, and release confirmed. These are follow-up labels, not official carrier or customs system statuses. Ask what an acknowledgement actually confirms: arrival of an email, readable attachments or completion of a particular requirement. DHL Israel describes document review that may lead to release, inspection or a request for more paperwork. Consequently, a receipt confirmation should not be recorded as release. Keep the wording, date and source of each update, including whether the provider is still waiting for another party.

Ask for the next action and a follow-up time

Send a concise follow-up using the existing case reference: what was requested, what you submitted and when, what receipt you have, and what remains unanswered. Ask the handler to identify the next action, its owner and when another update should be requested. If the agreed update is missed, use the provider’s published support or escalation route and retain the same case history. Separately ask whether storage or another time-dependent charge applies, its start date and any deadline requiring action. Do not infer a universal response time or free-storage period from another importer’s experience.

Keep the release and delivery handoff together

When release is reported, save the confirmation and ask what still needs to happen before collection or delivery. Identify the transport contact, any outstanding instruction and the reference needed for the next stage. Close individual document items only when their outcome is known; keep unresolved billing questions separate. The worksheet below can hold request and status references without storing identity documents. If you approach Israelepost for a new service enquiry, describe the goods, shipment stage and unresolved question first. The team must assess the service scope; a completed checklist does not grant authority to act or guarantee release.

Your preparation checklist

• Verified provider contact and submission channel: ______
• Shipment or airway bill reference and case number: ______
• Exact request, request date and goods/model covered: ______
• Requested item → document, issuer, version and owner: ______
• Submission date, attachments and receipt reference: ______
• Sent, received, accepted and released recorded separately: ______
• Open item, next action, responsible party and follow-up time: ______
• Applicable storage dates or action deadlines confirmed by handler: ______
• Release evidence, delivery contact and handoff instruction: ______