Shanghai Bunker Documents: Submission Is Not Completion

Key takeaways

• Identify the process stage represented by every electronic record.
• Do not use a submission receipt as evidence of an issued decision.
• Keep regulatory, supplier and delivery statuses separate.
• Obtain the actual final record needed for the specific review.

Digital processes still contain distinct decisions

Shanghai's published 2024 fuel-transition plan addresses paperless processes and green-fuel service development. Shanghai work plan

The plan's scope does not establish how a particular current application has been decided. The buyer must identify the actual record and status relevant to its transaction rather than infer completion from the existence of an online process.

For a current transaction, the document-stage review is not provided; obtain current verified information. Record the process, relevant application or delivery reference, evidenced stage, outstanding condition and responsible confirmation route.

Ask which process the status belongs to

A supplier's order platform, a payment workflow and an authority-facing application can all display accepted or completed while referring to different events. Identify the process before importing its label into the overall delivery plan.

For example, a supplier can acknowledge receipt of the buyer's request while a separate applicable condition remains unresolved. That acknowledgment may be useful evidence, but it does not answer every question about the proposed service.

Do not combine these positions into a single approved flag unless the relevant underlying decisions are actually established. A more precise status helps the incoming desk see what action remains.

Distinguish receipt from substantive determination

A submission acknowledgment can establish that information was received through a particular route. It should not be represented as a final decision unless the document actually provides that result.

Read any qualifications, requests for further information and limits attached to the response. A processing update may concern completeness of the submission rather than permission for the activity itself.

Where the legal or regulatory effect is uncertain, check the current applicable text and obtain competent clarification. Procurement should not determine the meaning from an icon, file name or a translated status word alone.

A digital-status review table

Fictional case: one completed workflow hides another open step

A fictional Shanghai buying desk receives a screenshot showing a submitted request as processed. It marks the bunker service fully approved and tells the next shift that no further document action remains.

A reviewer checks the underlying record and finds that processed refers to receipt and routing of the request. The actual decision needed for the proposed service remains pending under the applicable process.

The desk corrects the handover, identifies the outstanding confirmation and asks the responsible party for the relevant final evidence. The screenshot is retained for what it proves, but it no longer supports an unconditional service conclusion.

Connect the final record to the correct transaction

A valid-looking final document can still concern another vessel, product, date or service point. Match the relevant references rather than relying solely on the presence of an issued status.

If the programme changes after a decision, ask the responsible reviewer whether that decision remains applicable. Do not assume that a new supplier schedule automatically updates an external record.

Likewise, a replacement document should identify the earlier record it supersedes. The team should not combine different versions into an apparently complete approval that no single supported record actually provides.

Preserve access without creating a false duplicate

The review should retain an authorised way to retrieve or verify the relevant record when needed. A screenshot can assist a handover, but it may omit conditions or the supporting reference needed for later review.

Use an appropriate final copy or verification route under the applicable process. Do not assume that every export, preview or notification is the same as the issued document.

If the final evidence is unavailable, record the limitation and responsible next action. The absence of a convenient download does not justify inventing a completed status.

Keep the delivery and payment reviews independent

An issued process decision does not itself prove that the agreed fuel quantity was delivered or that the invoice is correct. Those conclusions require the relevant transaction evidence.

Conversely, receipt of an invoice or payment confirmation should not be used to fill a missing service-status record. Each review needs evidence that actually addresses its question.

A concise handover can therefore show several supported statuses without pretending they are identical. This is clearer than one broad completion label that conceals an unresolved dependency.

Common mistakes

Avoid treating submission receipts as final decisions, merging unrelated platform statuses and using screenshots that omit material conditions. Other errors include applying an old decision to a changed service without review or using payment evidence as a substitute for delivery documentation.

Where Zeaclub fits

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Zeaclub offers digitalised procedures across the voyage workflow.

Explore Zeaclub

Explore Zeaclub