Is there Multi-source syncing limits ?

50 bases in one view sounds like a base design problem (without knowing anything else about your use case). In my experience it sounds like trying to fit a Spreadsheet-like peg in a database-like hole.

I believe there’s an upper limit to how many syncs you can set up natively inside Airtable. You always have other options like Whalesync, or even tools like N8n or Make that watch for changes and write any changes found.

It is actually intended to centralize the inventories of multiple clients (around 50) into a single base.
This centralized base is then used to send all the data to a marketplace.
Each client manages their stock in their own individual base, which is then synchronized into the main centralized base.

I’d recommend consolidating it all into one base. Give users access to their own stock data, instead of giving them separate bases and then figuring out how to sync it all.
Tools like Softr/Zite have been supporting this use case for long. Even Airtable Portals would be useful here.

If you can sync it all into one base, chances are that you can just keep it all in one base and get rid of the 50 other bases.
Any other reason to keep 50 bases other than data silo/permissions?

I’d like to know whether this is possible or if there is a limit to Multi-source syncing.

On Teams you can do 10 synced tables, and on Business / Enterprise you can do 20 currently.  (See the Pricing page for confirmation: https://airtable.com/pricing)

As a (very clunky) workaround, maybe you could try creating multiple bases to get around the limit?  Not sure if this works, so I’d recommend trialing it with like 2 synced tables each first to confirm

1. Base 1: Sync tables 1-20, consolidate all 20 tables into a single table
2. Base 2: Sync tables 21-40, consolidate all 20 tables into a single table
3. Base 3: Sync the two conslidated tables from Base 1 and Base 2

This would be a bit of a nightmare to maintain though even if it did work though

---

+1 for VikasVimal’s suggestion to see whether you can do it from a single base instead!  You could then create an Interface that would only allow each client to see their own records

Given that you can sync their tables they should all have their own paid seats as well, right?  And so moving into an Interface only + Portals workflow might save you money in the long term too (https://www.airtable.com/platform/portals)

Specifically, a Teams seat costs $25, and a Portal bundle costs $120 for 15 people, and so once you hit 5 clients it’s cheaper to just get a Portal bundle instead, does that make sense?  Math changes a bit if you’re on Business though as it then becomes $150 for 15 people

​@El_Monu 

Oddly enough, Airtable doesn’t specify what the limit is for syncing multiple sources into a single table, but we can safely assume that it is significantly lower than 50.

However, the key problem that you’re facing is that your database system has been setup incorrectly.

As others have pointed out above, all of your data for all of your clients needs to be combined into a single base, and then you need to give your customers access to their own data by using a customer portal.

Costs will also depend on whether you need your customers to edit their data or just have read-only access to their data.

For now, I’m going to assume that you need your customers to edit their data.

Here are 4 ways of doing that — both paid and free:

1. (PAID) Use Airtable’s portals, which lets you add editors at a reduced cost. However, this reduced cost is still very expensive, and there is a minimum of 15 users. So you might want to turn to a 3rd-party portal.
    
2. (PAID)  Use a 3rd-party portal, which are less expensive than Airtable’s portals.
   
   The most popular 3rd-party portals that are currently available for Airtable are:
   Noloco, JetAdmin, Softr, Pory, Glide, and MiniExtensions.
   
   I gave an entire one-hour webinar on Noloco called Building a Client Portal on Noloco powered by Airtable.
    
3. (FREE) External read-only users can edit your Airtable records for free by using Fillout’s advanced forms for Airtable.
   
   Fillout is 100% free, and it offers hundreds of features that Airtable’s native forms don’t offer, including the ability to update Airtable records using a form.
   
   Fillout gives you a formula that you add to your Airtable base, which automatically creates a special URL for each record.
   
   Read-only users in Airtable are free, and they are allowed to click on URLs. (They are also allowed to click on buttons that take them to external URLs).
   
   So they would click on the the URL (or button) while looking at the record, which would take them to that record in Fillout.
   
   I show how to use a few of the advanced features of Fillout on these 2 Airtable podcast episodes:
   - Using Fillout to update an existing Airtable record & create an eSignature approval process with PDF file creation.
   - Using Fillout to create an order entry form with line items.
    
4. (FREE) External read-only users can edit your Airtable records for free by triggering a custom webhook in Make, which would then automatically run an automation that marks that task as complete.
   
   Same setup as #3 above. You would create a formula in your Airtable base, which would automatically create a unique webhook URL for each record.
   
   Then, your read-only user would click on the URL (or button) while looking at the record in Airtable, which would then trigger the automation.
   
   I demonstrate how to do setup these custom webhooks in this Airtable podcast episode.
   
   Note that my podcast episode demonstrate this in the context of putting the custom webhook URL inside of an email, but you can skip that step.
   
   If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread.

Hope this helps! If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld