E2V - Fast. Reliable. Scaleable.

Inventory Server

The Three Laws of Inventory Servers:

  1. You must always have one, and only one, primary Inventory Server rezzed.
  2. Your server should always contain all of your products.
  3. No matter what delivery mode you use, you will always need an Inventory Server.


More fun topics:

  • Location of the Inventory Server
  • Adding Storage Boxes
  • Customizing Storage Boxes
  • Suffixes
  • Backup Server
  • Preventing Redelivery
  • When You Don't Have Copy Perms


Location of the Inventory Server

The location of the Inventory Server affects the delivery process for your products. This is discussed at length in the article on delivery modes. Where ever your Inventory Server is rezzed, it can service any number of satellite stores anywhere on the grid.

Adding Storage Boxes

Every time the Inventory Server starts or resets, it will ask you for link permissions. Normally, it doesn't matter what you answer. Link permissions are required for adding new storage boxes only. If you try to add a new storage box, and you either didn't grant permission, or the server has since reset (it does that occasionally), it will simply ask you for permissions again.

A new storage box will appear above the root prim of the server. Once rezzed, you can use Edit Link Parts to move it within SL link set limits.

Customizing Storage Boxes

There are 3 simple customizations you can do to your storage boxes, if it helps to keep you organized.

First, you can recolor the white strips down the sides and back.

Next, you can replace the texture on the front where you see the "E2V" logo.

Lastly (recommended) you can rename the storage boxes. The reason for this is that customers may see the name of the box that sends them a delivery, so it's better if they see the name of your store (or whatever you choose) than the default name of the vendor system.

Suffixes

Normally, a vendor object's name must match the name of the boxed product exactly. This name matching is how the system knows which product to send for which vendor.

There are times, however, when it is advantageous to have variations between the two names. For example, let's say you have an item called "Blue Cube" for sale in your store. It comes in a bag that you should wear in order to unpack it. In this case, it makes sense to name the item "Blue Cube (Wear to unpack)" or something similar. However, this would require that the vendor have the same name, which is a bit odd, since you don't wear a vendor. This is where the suffixes feature comes in.

You can create a note card called suffixes, place one suffix per line and put the note card into the root prim of the server. A suffix is a bit of text that you want the system to treat as a possible ending for an object's name. To follow the previous example, if you add the text "(Wear to unpack)" in a suffixes notecard, then you can name your vendor "Blue Cube" and it will deliver an item from the server that is named "Blue Cube (Wear to unpack)" if there is no item named "Blue Cube" in the server. This works because the server fails to find "Blue Cube" and then tries tacking on the suffixes to locate a matching item.

Backup Server

You can (optionally) have one backup server rezzed on the grid. Some notes about backup servers:

  1. You create a backup server by taking a copy of your main server, rezzing it on a different region, placing a note card named backup in the root prim, and then clicking the server to activate it. (The contents of the note card are unimportant.)
  2. If your primary server lives on the same region as your store, and you don't have any other store locations, then a backup server is unnecessary.
  3. The Delivery Relay first tries to contact your primary server. If that fails, it then tries to contact your backup server. Once the Delivery Relay has switched to the backup server, it will not automatically switch back to the primary server, unless there is a problem contacting the backup server.
  4. You can manually force the Delivery Relay to switch back to the primary server by clicking the Delivery Relay, and picking "Reset" from its menu.
  5. Because of the above point, the contents of your primary and backup servers should be kept in sync, because the system could be using either one of them at any time.

Preventing Redelivery

If you have items that you do not wish to be eligible for redelivery, you can designate one or more storage boxes as "No redelivery" boxes. Do this by placing the text "nr" into the description field of a storage box, and then add items to it. The square on the front should turn yellow instead of green. Items in any boxes marked with "nr" will not allow the items contained in them to be redelivered.

When You Don't Have Copy Perms

If you are selling items for which you do not have copy permissions (i.e. when you sell one, it physically leaves the server), then you can make use of the [E2V-3] Stock Notify 3.x script as an aid to keeping track of how many copies of a particular item are left. Just place a copy of the script into each box that contains no-copy items, and it will IM you when the number of copies of an item in that box drops to 3 or below.