Search in documentation
ctrl+4K
Modules
Authentication
Merchant
Catalog
Order
Events
Logistics
Shipping
Review
Financial
Solutions
Shipping

Homologation criteria

Prerequisites

  • The application must be fully developed before homologation
  • Tests evaluate the entire application, not just API calls
  • Only Professional accounts (CNPJ) are accepted for homologation
  • Personal/Student accounts (CPF) will not be accepted

Applicability

These criteria apply to integrators who wish to integrate exclusively with the Shipping module to contract delivery services for orders outside the iFood platform.For integrators also using the Orders module:For already certified integrators:
  • Although not mandatory, we recommend performing Shipping module homologation
  • Ensures requests are correct
  • Allows early problem detection

Functional requirements

1. Event management

The application must:
  • Polling: Query the /polling endpoint every 30 seconds
  • Acknowledgment: Send /acknowledgment immediately after receiving events
  • Idempotency: Identify and discard duplicate events received in polling

2. On Demand order management

The application must be able to:

Order confirmation

  • Receive and confirm immediate On Demand orders
  • Parameters: orderType=DELIVERY, orderTiming=IMMEDIATE, salesChannel=POS

Order cancellation

  • Receive and cancel immediate delivery orders
  • Mandatory: Query cancellation codes via /cancellationReasons before requesting cancellation
  • Mandatory: Make reason list available in POS system for user selection

Status synchronization

  • Update status of orders cancelled by customer or iFood
  • Update status of orders confirmed/cancelled by other applications (e.g., Order Manager)

3. Address management

The application must:
  • Accept or reject address change requests
  • Process changes within established timeframe

4. Collection code

The application must:
  • Verify order collection code
  • Validate if code was confirmed by driver

Non-functional requirements

Performance and security

  • Token renewal: Renew only when about to expire or immediately after expiration
  • Rate limiting: Respect request limits for each endpoint
  • Error handling: Implement retry with exponential backoff

Monitoring

  • Log all critical operations
  • Implement alerts for integration failures

Desirable requirements

Although not mandatory, the following items are strongly recommended:

Receipt printing

Delivery observations

  • Display delivery.observations field on system screen
  • Print observations on receipt
  • Ensure visibility of special delivery instructions

Homologation process

1. Preparation

  • Complete application development
  • Validate Professional account (CNPJ)
  • Configure test environment

2. Testing

  • Execute all mandatory scenarios
  • Validate error handling
  • Test event synchronization

3. Approval

  • Review complete checklist
  • Fix non-conformities
  • Request final validation

Support

For questions about the certification process:

Next steps

After homologation approval:
  1. Migrate to production environment
  2. Configure continuous monitoring
  3. Establish operational support process
Was this page helpful?
Rate your experience in the new Developer portal:
On this page
Homologation criteria
Prerequisites
Applicability
Functional requirements
1. Event management
2. On Demand order management
3. Address management
4. Collection code
Non-functional requirements
Performance and security
Monitoring
Desirable requirements
Receipt printing
Delivery observations
Homologation process
1. Preparation
2. Testing
3. Approval
Support
Next steps
Content read0%