Nodes on Jet represent warehouses. It was designed this way so JET can see how many products are located in each warehouse, so that they can determine from which warehouse it is better for a seller to ship a product.
Simple scenario 1
Let's say you have just one warehouse and it is located in TX.
You need to go to Partner.Jet.com and add your new Node, which you will call for example Texas.
Now, GeekSeller sees this node and you can provide information how many products you have in this warehouse:
However, your business grows and you are opening a new warehouse in LA.
You need to login to Partner.jet.com and add a new node with a new location and you call the new node 'LA Warehouse'. It will be visible also via your GeekSeller interface and you can control qty of each SKU for both of your nodes / warehouses via GeekSeller interface.
On your GeekSeller account it will look as shown below. Qty 0 indicates you do not have a particular product in a given warehouse:
Simple scenario 2.
You sell on Amazon, part of your inventory you shipped to Amazon utilizing their FBA program. However, you also keep some products in your Warehouse in NJ.
You need to go to Partner.jet.com and create two nodes, one will be called FBA and it will store data about the available quantity of each product you have in Amazon warehouses (FBA). The other node will represent how many products you have in your NJ warehouse. When you sell on Amazon via FBM program it means that you ship purchased products on your own. When you sell on Amazon via FBM and FBA you can sell the same products in both programs. When you have more products to offer you just go to Amazon account and change the quantity of your FBM products.
In order to update your FBA quantities on Amazon you will have to ship them new items for inventory. In this case you always have your updated quantity on Amazon, so do not want to update quantity via GeekSeller interface. You want GeekSeller to get data from Amazon and send this to JET.
You need to first go to Partner.jet.com and create two nodes then via GeekSeller interface link them with your Amazon account.
In Extensions > Amazon you will indicate that FBA should be linked to FBA node, while FBM program to NJ Warehouse. At this point you will not edit qty in GeekSeller interface, you will manage qty on Amazon and GeekSeller submits data to JET.
On a product list you will clearly see that if a product has 0 on NJ Warehouse but a number larger than 0 on FBA node, this is FBA product.
Remember that if you sell the same product on FBA and FBM, they have different SKU, so they will exist in GeekSeller as two separate product, just one will have qty 0 on FBM and another one on FBA node:
Of course if you have more Amazon accounts you can linked them as well. Just remember that each FBM and FBA needs its own unique JET node. You DO NOT at this point make any edits to qty in GeekSeller interface, you make changes on Amazon and GeekSeller submits data to JET.
Of course you can add as many nodes as you want to JET. For example, you have GeekSeller pushing to JET information about qty you have on two FBA and two FBM nodes, so you update qty on Amazon and GeekSeller pushes it to JET. Then, you can add additional node, as shown below called Texas, which is not linked to any Amazon accounts of yours. That means you can now sell a product on JET, which you do not have on Amazon.
On GeekSeller this will look as follow, you have qty 0 for all the nodes linked to Amazon accounts, and you manage qty for this product which does not exist on Amazon via GeekSeller interface by editing qty in a node called Texas. Please note that if you put some qty to another node, for example FBA, GeekSeller will soon overwrite it with 0, because there is no such product on your FBA node.
You need to see nodes as baskets which keep information about qty of a product. If they are connected to GeekSeller only, then they are managed via GeekSeller interface manually by a seller. However, they can be automatically updated for example via EDI:
Nodes can be connected to external stores such as Shopify, where a seller may keep qty about products:
Walmart is a bit different than JET and they do not ask for multiple nodes, they have a one node, representing qty for a product in genral and they relay on a seller to decide from which warehouse to ship ap roduct.
GeekSeller allows selers to combine values from few JET nodes and submit it as a single value to Walmart:
As much as there are limits, we can technically connect things in a complicated way. For example as shown below we can connect there also Shopify which will udpate qty to Texas, and then we take a sum of all those nodes and submit to Walmart.
What is not possible is a situation in which we connect a node to two systems which try to update qty on this node. For example, you cannot connect Shopify to a node which is already connected to FBA, because FBA already sends data to the FBA node, we cannot ask Shopify to also send there qty information because both system will keep overwriting data for each each on the node.