# Related or unique shopping cart

**URL:** <https://community.glideapps.com/t/related-or-unique-shopping-cart/45288>\
**Category:** Ask for Help\
**Created:** [July 27, 2022, 12:26am UTC](https://community.glideapps.com/t/related-or-unique-shopping-cart/45288 "2022-07-27T00:26:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [July 27, 2022, 1:12am UTC](https://community.glideapps.com/t/related-or-unique-shopping-cart/45288/2 "2022-07-27T01:12:53Z")

</div>

> [@Editar los pedidos del carrito](https://community.glideapps.com/t/editar-los-pedidos-del-carrito/45281/3):
>
> Normalmente, la configuración ideal es: Una mesa para los artículos Una tabla para los artículos del carrito, aquí es donde sus vendedores añadirán artículos a cada pedido. Digamos que pido 1 coca y 1 hamburguesa, serán 2 filas. Asegúrese de que cada fila tiene un rowID (lo llamaré cartID) y capture el correo electrónico de la persona que agregó el artículo. Tener una pestaña que apunte a la tabla de artículos del carrito, filtrar por email es usuario registrado, y “añadido al pedido” n…

Basically it’s the same idea as above, but for each “Cart item” you would have the “Business rowID” in there as well.

In your User Profiles table, create a relation to check for un-submitted rows, and return the business rowID (a single value column).

If the user is trying to add an item with a business ID different from their “currently added business ID” as described above, then you don’t allow them to add.

---

_[View the full topic](https://community.glideapps.com/t/related-or-unique-shopping-cart/45288)._