I think I see the problem. In your example, with an Order record that contains links to Product and Customer, you are effectively using the Order record table as a junction table. This is entirely unnecessary and I believe it is complicating things beyond what you would consider an elegant design. In my mind, you have 3 tables.
The Order table’s primary column would be the Order Number, in that case I would have a Product table link that allows multiple records, and a Customer link that does not allow multiple records.
The Product table would have a primary column that is the name of the product, along with an Order link that would allow multiple records (recording every order that involved that product) and it would not need a Customer link unless you desired it for some kind of prediction or analysis to see what different customers or customer types tend to buy. But even if you did that, I would hide that column in the Product table because it would be massive, and instead I would use formula columns to analyze the number of times the product has been ordered for each customer type, or something like that.
The Customer table would have an Order link that would allow multiple records (recording every order that customer has ever made) and maybe a Product link, for the reasons stated in the above paragraph, and utilized similarly.
The important thing here is that the Order table is NOT simply a junction table. To be honest, creating junction tables is kind of difficult in Airtable. It requires a lot of convoluted stuff I don’t like, and you don’t need them because the individual record view feature can make that happen on the fly. If you want to see [select orders from customer where product = chairs] then you can simply drill into the customer record or something. And if you’re drilling into a record and you want to see a related record, you can drill into that from the screen you’re already on. See the attached pictures.
Maybe you should start with what you want to accomplish with your base, rather than what data you have available. In my experience you get more out of airtable when you are trying to answer a question that you’ve already got ready than if you just pour data into it trying to organize it. I’ll post a followup in a second to show you what I mean.