You can reach the live environment of the new IT Platform via this link:

https://prod.osapiens.cloud/portal

Yes, that is correct. In this instance, all three sites must be created, and the corresponding product(s) for each site must be created and appropriately assigned to their respective locations.

During the preparation of the Certification Scope work order, all products have to be added to the certification scope.

Please note that, depending on whether the Option 1 multisite producer is operating a QMS or not, the applicable certification option shall be selected (Option 1 multisite with or without QMS).

You will need to go to the existing certificate, press “Modify” which creates a new work order but with a copy of existing data, and then add the new product to the scope of the new work order.

Meaning in case of modification, it will be possible to create a new version of the audit with the same information that was filled in in the previous version. With this new version, a new scope can be assigned and a new version of a certificate can be created.

Please note that in case a certificate status was amended, e.g. suspended and reestablished, the modification audit functionality is not available. In this case, a new work order has to be created to include all information, including the new data. In case of Option 2, a new Certification Scope Work Order has to be created.

Yes, users that have assigned only the “Auditor” role in CertifierOS will have visibility into audits that are assigned to the particular Auditor within their respective CB. Access to additional general producer/CB information in CertifierOS will be limited for those COS users.

For more details please check the wiki below:
What are the user roles and rights in CertifierOS? – GLOBALG.A.P. Wiki Site

Yes. See here the relevant instructions.

Yes, this has previously been permitted in the Audit Online Hub as well.

No, because the process in the new IT platform follows a different workflow: First, the site(s) and PHU(s) must be created. Next, the products need to be created for each site/PHU. Finally, the products are assigned to their respective site/PHU.

Yes, these actions can be performed by the back office. Users will need to have the role “CB Assist / Audit Scheduler”.

Both alternatives are possible.

This functionality is currently in development and will be available in the future.

You can issue a PDF certificate using the templates available in the CB Extranet.

Yes, the audit name, date and time can be edited by pressing on the pencil icon and amending the relevant information.

You can make an excel but you won’t be able to upload it to the system.

Yes, this can be done via the API.

Yes. Please use the preprod-external test environment for testing purposes. In case you are experiencing any issues logging in, please contact the Stakeholder Helpdesk.

For sites and PHUs, you can enter either the full address if available (Street name, number, postal code, city and country) or the geo-coordinates.

In case the full address is not available, Geo-Coordinates shall be used.

• The producer has to be created/updated.
• All his/her site(s) & PHU(s) and products have to be created.
• The product(s) have to be linked to the respective site(s) and PHU(s).
• The audit has to be created, which will trigger the relevant P&C and attribute checklists (smart forms) according to the FAP, certification scope and reporting option.
• The audit needs to be assigned to the auditor(s). 
• The auditor(s) need to complete all checklists (smart forms) and close the NCs if applicable.
• The CB has to review the audit and take the certification decision by filling out the relevant smart forms. 
• The CB issues the certificate.

You do not need to necessarily use a different title each time. You can also change the title later.

As per the sites, it is advised to use a title that includes the Producer’s/PG’s name, GGN and a short description. e.g. “Name, GGN, Site apples” to be able to distinguish the sites later on during the process.

As per the product, it is advised to use a title that includes the Producer’s/PG’s name, GGN and a short description. e.g. “Name, GGN, product apples” to be able to distinguish the product later on during the process.

As per the audit title, it is advised to use a title that includes the Producer’s/PG’s name, GGN, audit type and date to be able to distinguish the audits in the future. E.g. “Name, GGN, IFA plants, recertification 28/02/25”.

CoC and CFM audits will still be possible in CertifierOS, despite this limitation in CB-AT.

Find the Chain of Custody (CoC) wiki here.

Find the Compound Feed Manufacturing (CFM) wiki here.

All members of the producer group, including the PG itself (if it engages in own production), must be listed under “Sub Producer” in the certification scope work order. This ensures that the system captures all relevant details to be reflected on the certificate.
For each sampled member, a separate work order shall be created.

Sites and products need to be added to the respective producers and producer group members. This can be done either manually via the web interface or the upload sheet.

The upload sheet is stored in CB-AT Portal.

Here is the direct link to the Bulk Upload Tool.

Yes, since this is mandated by the GLOBALG.A.P. General Regulations, the process remains unchanged. A dedicated tool to extract the audit report and NCs will be available shortly.

The same rules as per the GRs apply in the new GLOBALG.A.P. IT Platform. No difference from the past.

Producers can choose CBs per Product and Farm Assurance Product.

Find here additional information on the process.

As per the GRs, the site information needs to include the geo location information.

Each product must be registered separately for each individual site. For example, if a producer grows apples on two different sites, the apples need to be registered twice—once for each site.

For option 1 multisite without QMS, one CL for all sites shall be used. For option 1 multisite with QMS one CL per sample site shall be used.

Yes, API support will be provided, and the documentation can be found here.

This is depending on the definition of the site as seen in the GRs. In case of a single site with several plots, only one address has to be added. In case of an option 1 multisite, all sites/addresses shall be added.

Yes. A particular external PHU can be created as an asset to more than one producer.

No. Sites, products and (central) PHUs can be used indefinitely as long as they do not change.

For example, only if a new product is to be added to the certification scope, it has to be created and added to its respective site. The same applies for new sites and PHUs.

The CBs can use CertifierOS as a tool/platform to file evidence for the Accreditation Body assessment. If necessary, supporting documentation for corrective actions can also be uploaded.

For sites and PHUs, both methods are acceptable: either entering the complete address (including street name, number, postal code, city, and country), which allows the system to automatically calculate the geo-coordinates, or directly inputting the geo-coordinates.

If the full address is not available, geo-coordinates must be provided instead.

When generating the certificate, the system proposes the valid from/to dates. The valid from date is the current date and to valid to date is the current date +1 year -1 day. Both, however, can be changed.

In case the producer group has production of its own, the PG will be treated like a member. Meaning that it will be assigned as a member of its own producer group and products produced by the PG will be entered in the system the same way that it is done for the members of the PG.

There is no deadline to register a producer.

Find here the recordings for GRASP v2 option 1 and option 2.
All add-ons can be linked to the IFA audit in the same way.

Via the Scheme Manager access rights. Find here related instructions.

This feature is still under development.

Please note that one audit report (one work order) will contain the information for a single Farm Assurance Product. Therefore, only one audit type will apply per audit report.

Please note that multiple Audit Product Categories can be selected under the Plants scope.

Instructions can be found here.

Sites, PHUS and Products cannot be deleted. In case of a mistake, please use the pencil icon to rename the site or product. It is recommended to add a comment such as ‘invalid due to…’ to clarify the reason.

We recommend you to create a special “dummy” producer and assign the invalid sites and products to this producer.

Each Farm Assurance Product (FAP) requires separate work orders, which contain the applicable smart forms (P&C CL & attribute documentation) per FAP and need to be filled out separately.

Combined audits shall be linked. Find here the relevant recordings for Option 1 and Option 2 GRASP v2.

Please note that all add-ons shall be linked to the main IFA audit in the same way.

CBs must use CertifierOS as they do for options 1 and 2; however, they will select reporting options 3 or 4 instead. This will automatically trigger the relevant smart forms that need to be completed. Please note that benchmarked P&C checklists will not be triggered.

Regardless of the number of products, each audit/work order always includes only one P&C checklist.

Find here the instructions on how to install the mobile app on your iPhone and iPad. Please note that MacBooks are not supported.

Find here instructions on how to operate the mobile app.

An Option 1 with QMS audit is handled in the same way as an Option 2 audit.
It requires:

• one Certification Scope work order,
• one QMS work order and
• the number of site sample work orders based on the applicable sample.

Sampling procedures remain unchanged. A separate work order must be created for each selected producer group member.

Registration fees apply to each individual producer and to each producer group member. They will be charged either from the old system or from the new platform.

If a multisite producer does not operate a QMS, a single checklist will be used to cover all products and sites.

However, in the case of a Multi-site Option 1 with QMS, each sampled site must be documented in a separate work order, which includes the corresponding smart forms.

The producer will need to be transferred to the new CB by the Stakeholder Helpdesk Team (please contact stakeholder_helpdesk@agraya.com). The incoming CB will be able to create a work order after the producer is transferred.

Once the work order has been started, the producer can be transferred back in case they are working with more CBs for different Farm Assurance Products.

The provisions of the GRs shall be followed.

The LoC will be generated automatically by the IT platform after the assessment is finalised.

A new audit/work order has to be created and marked accordingly. E.g. “Modification audit“

In case of open non-conformances, the provisions of the GRs shall be followed.

This needs to be done before the audit.

Yes.

Corrective actions must be closed via the GLOBALG.A.P. IT Platform. The data can be entered by users with multiple roles from a CB, including auditors.
The CB can also use CertifierOS to upload and store evidence of the corrective actions.

Find additional information here.

Feel free to test only in the Test (Preprod) environment.

Producers and PGs can be deleted. The ability to delete sites and products will be introduced in a future update.

It is a limitation of the system that you need to re-enter the level of the NC.

The due date has to be added manually to the smart form and NC ticket directly after raising the NC.

There will be one P&C checklist regardless of the number of products. In addition, there will be one smart form per product for the product attributes.

The producer will need to be transferred to the new CB by the Stakeholder Helpdesk Team (please get in touch with stakeholder_helpdesk@agraya.com). The incoming CB will be able to create a work order after the producer is transferred.

Once the work order has been started, the producer can be transferred back in case they are working with more CBs for different Farm Assurance Products.

Yes, it is.

Correct, also for single site producers.

No, the Excel upload of a checklist is not possible. The mobile application shall be used, or an API connection shall be established for offline auditing.

No, it is not possible.

A site shall be created only once. The respective product(s) need to be linked to the respective sites where they are cultivated. More than one product can be added to each site.

Yes, it is possible.

The auditor is required to complete the P&Cs in accordance with the GR and accreditation requirements. This aspect remains unchanged compared to the AOH process.

No, you can perform the audit through the user web interface, the mobile app (which also works offline), or by integrating via an API.

Currently the checklist is available only in the English language.

Unfortunately, this will not be feasible, as the audit scope is required to be defined while connected to the online system.

No, due to a limitation of the system. When the connection to CB-AT is established, GAINs will be assigned automatically.

No, but there is a possibility of using an offline mobile application (available for Android Windows and iOS) and synchronising the audits/work orders with the online GLOBALG.A.P. IT Platform.

Please note that Apple computers are not supported. The mobile app is working only on iPhones and iPads.

There is no technical integration between IFA and GRASP, nor between any work orders that would enable such cross-verification. The GRASP checklist will ask if the particular IFA worker welfare P&Cs have been complied with.

There will be a similar role called CB assistant. This role can execute many actions, but it is not a role where the assistant is assisting a particular other users.

Yes, each product has to be created and added to the respective site.

Note: Sites, PHUs and products need to be created only once and can be used for all future audits.

Yes, the relevant smart forms that include information available before the audit can be filled out after the creation of the work order.

This is a limitation of the system. If you only send the locationID, the address and other details deemed mandatory will not be registered in the report.

You can import the whole process at once. Notice, however, that the answers to the smart forms need to be submitted via separate API calls, non-conformance tickets need to be created and assigned separately, and there is a specific call for the work order status change.

From an API perspective, at any point in time you can send the data via the API.

Multiple products per site/PHU are possible. However, they need to be added individually one at a time to the PHU.

Find here the preprod (test) environment: https://preprod.osapiens.cloud/portal/portal.html

You need to name the product to be able to distinguish it and to be able to select it further on in the process.

Find here additional information.

The process will be very similar to the process presented for IFA. In case of benchmarked standards, there will be less information to be completed before issuing a certificate (The P&C checklist of the benchmarked schemes shall not be filled out in the new GLOBALG.A.P. IT platform).

Each work order will have a task set by default by the system so that the system can generate the necessary smart forms. While a user can technically create more tasks, this should not be done since it creates unnecessary additional smart forms. In that sense, the tasks section can be ignored so that the tasks created upon audit generation are left and no new tasks are added.

This functionality is not available when offline when using the mobile application.

However, if an internet connection is available, sites and products can be added during the audit via the web interface, the upload sheet, or the API.

Under “Sub Producer”, all producer group members will be added. In case PG itself has production sites with products, PG will be added as well as “Sub producer” as well.

Under “Scope Information” the products registered with dummy “PG/multisite scope information” Site,  PG´s own production sites, the PHU(s) and the producer group members sites have to be added.

Auditors will have access only to audits assigned via “Team Roles” functionality located on the right hand side column of the Audit template with the respective CB that the Auditor has an account with.

Please check the wiki below:

How to assign roles to an audit (Auditor(s), Reviewer, Decision-Making-Committee) – GLOBALG.A.P. Wiki Site

The certificate will display both the geographic coordinates and the corresponding marker on the map.

The PHU(s) that belong to a producer group member shall be added to this member in the same way as if it were an option 1.

All LoC and certificates will be generated via the new IT System Platform.

O-keys will not be used in the new GLOBALG.A.P. IT Platform.

The product attributes will be added via the smart form section at the bottom of the audit work order. There will be one smart form per product/site that contains the attribute data fields.

For technical reasons, geo-coordinates must be provided with six decimal places. If your data currently includes only four decimal places, please append two zeros at the end of each coordinate value. For example: 21.1234 should be adjusted to 21.123400.

Please note that each license key is valid for a single use only. If a mobile application user intends to operate the app on multiple devices (e.g., one Android and one Windows device), they must be provided with a separate license key for each device.

The assigned audit information will nevertheless be synchronized across the devices for this single user.

Currently, this is a system limitation but we have taken note to improve the user experience in this use case.

Yes. All audits starting from 03/11/2025 shall be conducted in CertifierOS.

The registration fee for plants is calculated based on the area registered under first harvest for each crop. Any area that is used more than once in an annual certificate validity (certification cycle), for the cultivation of the same product only, shall be registered as further harvest. Areas registered under further harvest of the same product, are not subject to additional registration fees. Product quantity changes during the validity of a certificate may also result in changes of the registration fee.

As the GLOBALG.A.P. database is planned to be shut down, QS-GAP-related standards (and their processes) will be handled solely in CertifierOS.
See here our related wiki

Yes, but please note that the product numbers are different in the new IT System.

The content will be primarily available in English as the default language. However, we will progressively include other languages in the system.

No, paper certificates will no longer be issued. All certificates will now be generated exclusively through the new IT System platform.

An audit report generation will be made possible, which will also include an overview of the NCs.

Certificate data can be retrieved through the API.

Audits, producers & sites/products/PHU can be filtered via the search. Search is possible via name, GGN, Audit ID, Site title and Site ID.

Yes, the PDF certificates will be generated via the CertifierOS.

The related recording shall be shared soon.

As an alternative, find her the related Wiki.

Yes, this can be done via the API.

CB-AT is connected to the new IT platform and CB-AT will remain operational to support auditor approvals.

All user accounts of the new platform must be created directly in CertifierOS manually. Each CB’s Scheme Manager (SM) will have the necessary permissions to create new users, following the instructions provided here.

Integration between CB-AT and the new IT platform is implemented for the FAP approval process. This means that approved FAP information is migrated to COS user accounts almost in real time.

Please check the wiki below:

How to add Farm Assurance Products to an auditor user (FAP approvals) in CertifierOS – GLOBALG.A.P. Wiki Site

This is due to a system limitation and will be fixed in the future.

This is a system limitation. In the future, it will only need to be selected once per work order.

Geo-coordinates for sites are mandatory based on the GLOBALG.A.P. Registration Data Requirements.

Producer and PG master data will be migrated from the Database to the new GLOBALG.A.P. IT Platform.

Sites and their respective products were never introduced in the Database and have to be created in the new GLOBALG.A.P. IT Platform.

No, the producers can be registered only by the Certification Bodies.

The certificate issued in the new GLOBALG.A.P. IT platform will not automatically recognize the previous certificate from the GLOBALG.A.P. Database. It is the Certification Body’s responsibility to select the correct validity dates (both start and end dates).

Yes, the order of the geo-coordinates has been corrected since version 3.17

Only the certificate information available in the GLOBALG.A.P. database will be migrated to the new GLOBALG.A.P. IT Platform.

The user interface is available in English, Spanish, French, German, Portuguese and Dutch.

Please note that some parts of the interface are only available in English for the time being. The remaining translations will be added soon.

You can select the desired language via the user profile.

Certified is used for FAPs where certificates are issued (all standards and Nurture Module add-on).

Assessed is used for GRASP, instead of “audited”.

For other add-ons (excluding GRASP) we refer to “audits” (so producer are audited) , but as they get a LoC, their production processes are not “certified” but “compliant with e.g. SPRING add-on”.

Yes, that is correct. This ID is the Organisation ID, which can be found in the web interface.

Only the Organisation ID (previously the o-key) of the CB is necessary for the upload sheet.

Yes, this feature is planned for a future update.

Yes, this is correct. The CBs that shared GGNs with the trustee CB will not have access to the GGN automatically in CertifierOS. In this case CB needs to request GGN sharing from Stakeholder Helpdesk.

A modification audit has to be created for the PG. The PG, all members, sites, PHU(s) and their product(s) need to be created and added to the certification scope work order. A work order for the affected producer group member has to be created and audited. 

Yes, this is possible.

The producer master data and certificates will be transferred. 

Note: The products and their attributes will not be transferred. 

The legal entity master data will be transferred to the new system. Since there is no information in the GLOBALG.A.P. database about sites, the complete data about sites, PHUs and products must be entered into the new system.

This can be done with the help of the bulk upload sheet or directly via the web user interface. 

Note: The bulk upload sheet is shared in the CB-AT Portal.

Here is the direct link to the Bulk Upload Tool .

As the GLOBALG.A.P. database does not support site creation for the producers, the sites need to be created in the new IT System and be assigned to the producer.

No. Only the certificates and producer/PG master date will be migrated from the GLOBALG.A.P. database into the new IT Platform.

Yes. At least one site and one product per producer/producer group member need to be created.

Please note that you can add more than one product to one site. 

A PHU and their product(s) shall be added only if applicable. 

The same applies also in the case of a PG which has its own production. The difference here is that for a PG, a “Central PHU” shall be added. 

Please note that the same applies also to benchmarked schemes.

Audits cannot be deleted from the system; however, they may be renamed if necessary.

For instance, in the event of an error where an audit must be disregarded, it is recommended to rename it using a clear and descriptive format such as:

“Producer Example Name, GGN, IFA F&V Initial – INVALID AUDIT”

This approach ensures transparency while maintaining the integrity of the audit records.

Yes, this is possible.

You can find here the recordings for the CertifierOS 

You can find here the information regarding the Mobile application (for offline use) 

You can find here the information regarding the bulk upload tool 

You can find here the recordings for the Supply Chain Portal 

When an audit is assigned to the mobile app of an auditor, she/he will receive a push notification (pop-up message) if this feature is enabled on her/his device.  

Please note that this feature has to be enabled on the device platform settings.

Everything that needs to be listed on the certificate must be included in the Certification scope work order of the Option 2. 

This includes all producer group members, PG’s own fields (if applicable), all PHUs (central, external, and member), and all products. 

First, you need to create a producer, her/his sites and products as seen in the recordings.

Next step is to add the newly created producer to the PG as seen here at minute 1:49.

Yes, all sites and PHUs (if applicable) and their respective products need to be created.

Browsers where users can download certificate PDFs or Audit Reports:

• Google Chrome
• Microsoft Edge
• Opera

Browsers where users can NOT download PDFs:

• Firefox
• Safari

Non-conformances will be handled via the IT platform as seen in this video. The report will be generated through the IT platform. 

The certificate issued in the new GLOBALG.A.P. IT Platform will not automatically recognize the previous certificate from the GLOBALG.A.P. Database. It is the Certification Body’s responsibility to select the correct validity dates (both start and end dates).

A checklist cannot be uploaded and must be manually completed either in the web interface, the mobile application or via API.

You can find the training videos here. 

If you still face any challenges, please share the details with our Stakeholder Helpdesk Team. Please make sure to share the producer/PG name, GGN, audit ID, CertifierOS environment (Live or preprod) and related screenshots. 

The existing producers will be migrated to the new platform. The ones that have valid certificates can be found via the Supply Chain Portal.

The CBs own producers/PGs will be visible on their producer list in CertifierOS.

The platform is still under development in cooperation with our developers. The “External ID” field will soon be renamed to “GGN”.

Take a look at our wiki with the newly introduced terminology.

Yes, more than one staff member can work on a work order. E.g., administrators can add general information, and the auditor will fill out the audit-related smart forms.

Through the mobile application, work orders can be split between auditors. In such cases, auditors must coordinate to prevent overlapping tasks.

Yes, the auditors who have only “Auditor” role assigned to their user account in CertifierOS will have access only to audits that are assigned to them via “Team Roles” function directly from the Audit template/Work Order. More information in this wiki article: How to assign roles to an audit (Auditor(s), Reviewer, Decision-Making-Committee) – GLOBALG.A.P. Wiki Site 

Auditors who have assigned combined “Auditor (Farm or QMS) & CB Assist” role will have access to extended CertifierOS functionalities (including all CB audits) except to those functionalities that are intended for the Scheme Manager role.

In case you need any assistance, please contact the GLOBALG.A.P. Stakeholder Helpdesk . 

Please refrain from contacting the osapiens support directly.

Please contact stakeholder_helpdesk@agraya.com.

Your request shall include the new users’:

• surname(s),
• name(s),
• e-mail address(es),
• GAIN(s),
• Farm Assurance Products they are assigned for (E.g. IFA F&V, GRASP, SPRING, etc.),
• The certification option the auditors are approved for (Option 1/2).

If you are requesting credentials for multiple users, please provide the required information in an Excel file.

The GLOBALG.A.P. IT Platform will generate new passwords for the live environment.

While usernames will stay unchanged, new passwords will be automatically generated and distributed to the users of the pre-production environment.

Please note: In case any login credentials are missing, please contact your scheme manager. He will be able to create them for you.

Please contact the Stakeholder Helpdesk team for this action.

In the Supply Chain Portal, the system for validation of certificates, search, and bookmarking services will be launched on 3 November 2025.

Find here the link for the Live Supply Chain Portal (SCP).

And here is the link for the Preprod (test) version of the SCP.

Initially, the upload sheet will be used only for creating and modifying sites/products/PHUs. For sites & PHUs, Geo-coordinates are requested by the standard. 

Producers have to be created via the webform or an API and require an address. 

Currently, the bulk upload sheet will only allow for the creation & modification of sites & products. 

The audit process in CertifierOS does not support Excel file uploads.

Related recording shall be shared soon.

Correct, each line must be a different product, regardless of the option of the producer. The only case where this is not true is when the producer is auditing the products for a standard and one or more addons. In this case, the products must be repeated, along with a separate scheme ID.

Yes, it will be available to test in PREPROD. 

For the time being, the upload sheet can be used to create new/amend sites/PHUs, Products, and link the products to their respective sites/PHUs. 

In the future, the upload sheet will be used in addition to the above to create new producers/PGs, link the PG members to the PG, create audits and issue certificates. 

No, the upload sheet size is not limited.

The upload sheet is located in the footer of the CB-AT Portal.

Here is the direct link to the Bulk Upload Tool.

The program will first validate that all information is in the correct format. In case there are any errors in the format, the exact cell in the worksheet will be marked along with a note explaining what is wrong. After uploading the sheet, any GGNs which could not have their data uploaded will be marked, along with the error message.