Ritzy One • Liner • Bahrain
Generate and submit a Liner voyage's WCO cargo manifest to Bahrain's OFOQ / Trade Facilitation Platform (TFP) Single Window — straight from the Liner job, with submission tracking and status re-checks.
The Customs Manifest action appears on a saved Liner job only when all three hold:
BAHRAIN (System Settings → Company & Tax).LN) is licensed.The credentials are stored as application settings (KEYPAIRS). Set these keys (via the DBA/settings tools):
| Key | Meaning |
|---|---|
BH_API_ENDPOINT | TFP manifest API URL (e.g. the OFOQ /tfp-serviceā¦/api/v1/manifest/sea endpoint). |
BH_API_USER | API username (Basic auth). |
BH_API_SECRET | API password/secret (Basic auth). |
BH_DECL_OFFICE | Optional — Customs declaration office code. |
BH_SUBMITTER_ID | Optional — submitter registration/TIN (defaults to the company CR/Business No). |
The manifest is built from the Liner job. These fields must be complete or submission is blocked:
Open a saved job → Customs Manifest. In the drawer:
Every attempt is kept in the submission log at the bottom of the drawer (reference id, type, manifest number, status).
| Symptom | Fix |
|---|---|
| No Customs Manifest button | Company country isn't BAHRAIN, Liner module not licensed, or API keys not set. |
| "credentials not configured" | Set BH_API_USER/SECRET/ENDPOINT in settings. |
| Missing-field warning on submit | Complete the listed header / BL / container fields, then retry. |
| HTTP 401 / 403 from customs | Verify the API user/secret and endpoint URL. |
| Rejected / validation errors | Open the log row's status; correct the flagged data and resubmit (an Amend is sent automatically once a manifest number exists). |