Skip to main content
This guide explains how to keep your Business information synchronized between your internal system and Partoo.
You’ll learn how to update, create, and manage businesses through the Partoo API, and how to choose the right synchronization strategy.

​
Prerequisites

  • You already store Business data (e.g., opening hours, addresses, names) in your internal system.
  • You have API access to Partoo with the appropriate credentials.
  • You are familiar with Partoo’s Business Update endpoint.
For most integrations, updating businesses through the API is the core synchronization step.

​
Identify the Business to Update

To update a Business in Partoo through the Business Update endpoint, you must uniquely identify it. You can do this in two ways:
  • By business_id (immutable identifier generated by Partoo).
  • By code (a customizable identifier).
Check the documentation of the Business Update endpoint for more details.

​
Using business_id

Best choice if you can store and maintain Partoo’s unique identifier.
Benefits
  • Immutable, unique, and permanent.
  • Guarantees no synchronization issues.
Drawbacks
  • Requires you to store the business_id in your system.
  • You must initially import and save existing business_ids.
  • When creating businesses via API, you must capture and store the new business_id.
Best choice if you already have an internal identifier for businesses.
Benefits
  • Flexible: you can assign your own internal ID to the code field.
  • Simplifies integration, since you don’t need to store Partoo’s business_id.
Drawbacks
  • The code field can be modified by API or directly in Partoo, which may cause desynchronization.
  • Codes are sent to Google Business Profile (GBP). Changing them may lead to issues with existing GBP locations. Contact your Partoo account manager before changing codes.
  • Not supported when creating businesses at the PROVIDER level.

​
Business Creation

After setting up updates, about 80% of the work is done. Next, decide how to handle new Business creations:
  • Low volume (<10 per year): Create businesses manually in Partoo, then let your automation update them.
  • High volume: Automate creation with the Business Create endpoint. If you’re using the business_id method, then save the returned id into your database.

​
Business Deletion

Even though there is a Business Delete endpoint, deleting is not always the best option.
  • Recommended: Set status = closed with the Business Update endpoint. This informs Google Business Profile and other platforms that your business is permanently closed.
  • Optional: Use the Delete endpoint later if you want to remove the business entirely from Partoo.
Deleting a business does not set it as permanently closed in GBP. Use status=closed first.

​
Partial vs Full Data Synchronization

If your system doesn’t contain all business fields, you can still use a hybrid approach:
  • Automated updates via API: Key fields such as name, description, opening times.
  • Manual updates in Partoo: Optional fields that your local users manage.
You can configure in Partoo which fields are editable by BUSINESS_MANAGER and GROUP_MANAGER roles. This allows you to control the key fields of your brand, while giving your users the possibility to fill the rest of the details that they master about your Business.

​
Sync Frequency

You control when synchronization happens. Two main strategies:
  1. Scheduled syncs
    • Run every 6 hours, daily, or at another fixed interval.
    • Send only the Business data that was updated on your system since the last sync (if possible).
    • If not possible, you may sync all businesses, but be mindful of rate limits.
  2. Event-driven syncs (recommended)
    • Trigger a sync immediately after data changes in your system.
    • Ensures Partoo always has the freshest data.

​
Next Steps

  • Review the Business Update endpoint reference.
  • Decide whether you’ll use business_id or code as your identifier.
  • Map the fields from your system to the ones available on Partoo, and chose the ones to sync to Partoo.
  • Choose a sync frequency that balances performance and data freshness.
  • Test your workflow with a few businesses on Sandbox environment before moving to Prod.