SFDA Ghad Account Setup for Food Companies
Learn SFDA Ghad account setup for Saudi food companies, including establishment access, user control, product data, documents and common setup errors.
7/3/20267 min read
SFDA Ghad Account Setup and User Access for Food Companies
Reviewed by: Saudi Food Registration Regulatory Team – Food Compliance & SFDA Advisory
Incorrect account, establishment and product setup can delay food registration before the technical review even begins.
For Saudi food importers, manufacturers and distributors, the main objective is not to create an elaborate portal hierarchy. It is to ensure that the correct legal establishment, authorised users, product records and supporting documents are connected accurately through the applicable SFDA systems.
This guide explains SFDA Ghad account setup for food companies, including establishment access, user control, product-data alignment, document readiness and common errors that can prevent a company from completing registration activities.
SFDA Ghad Account Setup: Quick Answer
A food company preparing to use Ghad should confirm that:
The account is created for the correct user and establishment type
The Saudi legal entity information is accurate
The commercial activity matches the intended food operation
Establishment and warehouse details are current
Only authorised users can access or manage applications
Product information is linked to the correct establishment
Company names and addresses match the supporting documents
Access remains controlled when employees, consultants or distributors change
The exact user options available may depend on the service and account type shown inside Ghad.
Businesses should follow the roles and permissions displayed in their active account rather than relying on unofficial role names.
What Is the Ghad Platform?
Ghad is an SFDA electronic platform used across regulated sectors, including food.
For food companies, Ghad may be involved in establishment-related services and product-registration activities, depending on the service being used.
The SFDA’s food-manufacturing licensing service, for example, instructs applicants to log in to Ghad, create an account based on the relevant user type and submit a facility-registration application.
Ghad account setup should therefore begin with the legal entity and regulated activity, not with the product alone.
Do Food Companies Have Standard Portal Roles?
Companies may need different users to perform different operational tasks, but public SFDA food guidance does not establish one universal hierarchy using the exact titles:
Company Admin
Establishment Account
Product Registrant
Local Agent
These terms should not be presented as mandatory official food-sector roles unless they appear in the company’s current Ghad interface or an applicable official guide.
A safer internal structure is to distinguish users by responsibility.
Recommended Internal User Responsibilities
Primary Account Owner
The primary account owner should be a person authorised by the Saudi legal entity.
Responsibilities may include:
Maintaining the main account
Confirming establishment information
Controlling user access
Reviewing important submissions
Removing access when staff or service providers change
Ensuring that account-recovery details remain current
Avoid relying entirely on the personal email address of a temporary employee, distributor representative or external consultant.
Regulatory Submission User
A regulatory employee or authorised consultant may prepare establishment or product information.
Responsibilities may include:
Preparing registration data
Uploading product and establishment documents
Reviewing labels and supporting files
Responding to authority queries
Maintaining submission records
The company should ensure that this user is formally authorised and that important records remain accessible to the Saudi establishment.
Review or Approval User
For larger companies, a separate internal reviewer may check information before submission.
The reviewer can verify:
Legal entity details
Manufacturer information
Product classification
Label artwork
Formula data
Supporting certificates
Product and establishment consistency
This is an internal governance recommendation, not an official SFDA role category.
Step 1: Confirm the Correct Saudi Legal Entity
Before configuring user access, confirm which Saudi entity will hold responsibility for the food activity.
This may be:
A Saudi food importer
A Saudi distributor
A local food manufacturer
A warehouse operator
Another licensed food establishment
The SFDA’s older food-registration materials describe the system as covering importers, domestic and foreign food establishments, warehouses, authorised agents and food products.
However, a foreign manufacturer should not assume that it can import food commercially without an appropriately established Saudi importer or responsible local entity.
Step 2: Match the Account to the Correct Establishment
The establishment information entered in Ghad should match the company’s official records.
Check:
Legal company name
Commercial registration number
Licensed activity
National address
Establishment address
Warehouse details where applicable
Contact information
Responsible user information
Differences in spelling, address format or company identity can create confusion when registration data is compared with certificates, labels or shipment documents.
Step 3: Use Controlled Company Email Addresses
Where possible, the main account should use a controlled company email address rather than an address belonging only to:
A former employee
A distributor representative
A temporary consultant
A third-party broker
A manufacturing partner
The company should also maintain access to:
Password-recovery methods
Registered mobile numbers
Verification messages
Submission notifications
Authority correspondence
Losing access to an email account can interrupt submissions and make user-management changes more difficult.
Step 4: Limit User Access to Actual Responsibilities
Not every user needs full control of the account.
Access should be limited according to the user’s job.
For example:
Management may retain ownership and approval control
Regulatory staff may prepare and submit files
Quality teams may review formula and certificate information
Label teams may provide artwork without managing the full account
Consultants may receive only the access needed for an agreed project
The exact technical permissions available should be confirmed inside the current Ghad account.
Do not assume that the same options apply to every establishment or service.
Step 5: Prepare Authorisation Documents Where Needed
When a consultant, employee or third party acts on behalf of the legal establishment, the company may need evidence of authorisation.
Depending on the service and case, supporting evidence may include:
Authorisation letter
Power of attorney
Delegation letter
Employment evidence
Company letter
Identification documents
Arabic translation
Attestation or legalisation where applicable
The wording should clearly identify:
The authorising company
The authorised person or organisation
The permitted scope
The validity period
The authorised signatory
Do not state that one specific PoA or LoA format is universally mandatory for every food-account activity.
Step 6: Link Products to the Correct Establishment
Product records must correspond with the establishment responsible for the registration or import activity.
Before entering product information, confirm:
Saudi importer
Foreign manufacturer
Manufacturing site
Warehouse where relevant
Brand owner
Country of origin
Product category
Pack sizes
Product identifiers
A product should not be connected to an unrelated manufacturer, outdated establishment or former importer.
This becomes especially important when a business has:
Several Saudi establishments
Multiple manufacturers
Several production sites
Private-label products
Contract-manufactured products
More than one distributor
Step 7: Keep Product Data Consistent
Account access alone does not prevent registration problems.
Product data should remain consistent across:
Ghad product information
Arabic label artwork
Ingredient list
Manufacturer documents
Certificates
Commercial invoice
Shipment description
Barcode and GTIN records where used
A GTIN is a commercial product identifier. It should be accurate, but it should not be presented as an SFDA user role or the only cause of a shipment hold.
The more important issue is whether the product identity is consistent across the regulatory and commercial records.
Common Ghad Account Setup Errors
Using the Wrong Legal Entity
The account or application is created under a company that is not responsible for the relevant food activity.
Corrective action: confirm the Saudi establishment, commercial activity and supporting licences before preparing product submissions.
Company Information Does Not Match Documents
The company name, address or registration number differs across the account and supporting files.
Corrective action: align the establishment record with current official documentation.
Account Access Is Controlled by a Former Employee
Important verification and recovery details remain connected to someone who has left the company.
Corrective action: transfer control to a current authorised company user and update recovery information.
External Consultant Has Unrestricted Long-Term Access
A consultant retains access after the project has ended.
Corrective action: review and remove unnecessary access according to the company’s internal controls.
Product Is Connected to the Wrong Manufacturer or Establishment
The registered product data does not reflect the actual production or import arrangement.
Corrective action: review the manufacturer, site, importer and product relationship before submission.
Several Users Submit Conflicting Information
Different users upload different versions of the label, formula or certificates.
Corrective action: establish one controlled final version and one internal submission owner.
Old Establishment or Distributor Information Remains Active
A former commercial arrangement is still reflected in the account or product records.
Corrective action: review the applicable update process before importing under the new arrangement.
What to Do When a Submission Remains in Draft
A draft status does not always mean that the user lacks a specific official role.
Check:
Whether all required fields are completed
Whether mandatory documents are attached
Whether the establishment is active
Whether the user has access to the relevant service
Whether the product is connected to the correct establishment
Whether an application step remains incomplete
Whether the account requires additional verification
Whether the platform displays a technical error
Capture the exact error message before changing account permissions or recreating the application.
Changing Employees, Consultants or Distributors
User access should be reviewed whenever the business relationship changes.
The company should:
Remove unnecessary account access
Update contact and recovery details
Preserve copies of submitted applications
Preserve authority correspondence
Record open queries and application status
Confirm ownership of labels and technical files
Verify that product records reflect the current responsible establishment
A distributor change may also require a broader regulatory assessment beyond user-access changes.
For that situation, review the separate guide to switching SFDA distributors in Saudi Arabia.
Ghad Account Setup Checklist
Before submitting establishment or product information, confirm that:
The account belongs to the correct Saudi legal entity
Commercial and licensed activities are appropriate
Company names and addresses match official documents
The main email and mobile number are controlled by the company
User access is limited to actual responsibilities
Authorisation documents are valid where required
The correct establishment is selected
Manufacturer and production-site details are accurate
Product records use the current information
Final labels and technical documents are controlled
Former users no longer have unnecessary access
Copies of submissions and authority responses are retained
How Saudi Food Registration Can Help
Saudi Food Registration supports food importers, manufacturers and distributors with:
Ghad account-readiness reviews
Establishment-data checks
User-access and responsibility mapping
Authorisation-document review
Product-to-establishment consistency checks
Manufacturer and importer alignment
Label and product-data validation
Submission-file preparation
SFDA query-response support
Account and application issue review
Support is based on the actual company structure and the options available in the current SFDA system.
Saudi Food Registration does not replace the legal responsibility of the registered Saudi establishment or guarantee authority approval.
Frequently Asked Questions
Does Every User Need Full Ghad Access?
No. Access should be limited according to the user’s real responsibilities and the permissions available in the account.
Can a Consultant Own the Main Company Account?
The Saudi legal establishment should retain effective control of its main account, recovery information and submission records.
A consultant may assist with submissions, but the company should avoid permanent dependency on an external party.
Does a Foreign Brand Need a Local Agent?
A foreign manufacturer normally needs an appropriate Saudi importer or responsible local establishment for commercial food importation.
The term “local agent” should not be used as a universal food-registration requirement without confirming the applicable legal and regulatory arrangement.
Why Is an Application Still in Draft?
Possible causes include incomplete fields, missing documents, inactive establishment information, insufficient service access or a technical system issue.
Review the exact message displayed by the portal before changing the setup.
Should GTINs Match the Product Label and Invoice?
Commercial product identifiers should remain consistent where they are used.
However, GTIN alignment is only one part of a wider consistency review covering product name, pack size, manufacturer, label and shipment documents.
Set Up the Account Before Preparing the Submission
A technically correct food product file can still be delayed when the account, establishment or responsible users are not configured correctly.
Before submitting a facility or food-product application, confirm that the Saudi entity, user access, authorisation documents and product relationships are accurate.
Contact Saudi Food Registration or use the website chatbot for a structured review of your Ghad account setup, establishment information and product-submission readiness.
Related Saudi Food Registration Guides
How to Avoid SFDA Delays Guide
SFDA Product Testing: Avoid Delays & Get Approved Fast
KSA Customs Holds: Border Testing Causes & Prevention
See Private Label & CMO in KSA: SFDA Ownership & Liability for PL and CMO approval control.
See ZATCA–SFDA Cross-Checks: Avoid Border Holds for how mismatched HS or GTIN data can trigger customs delays in Saudi Arabia.