Upcoming Export Format

With the introduction of the export feature (coming soon), you’ll be able to download your sales history and your store credit balances.

Both types of exports will result in a .zip file that contains a .csv file.

A single line from the sales history export looks like this (please note that the line wraps because of the blog format, there’s no wrapping in the file. Each transaction is one line, terminated by carriage return/line feed):

"DavidThomas Scorbal","ad7b01b9-9b71-4beb-ba05-0c353ade5952","Big Blue Box","2017-09-01 09:12:41","BlackFish","125","C","",""

The columns, in order, are:

Purchaser Name 
Purchaser UUID 
Item Name 
Purchase Date 
Purchase Region 
Price 
Payment Method (L = lindens, C = credit) 
Recipient Name (blank unless bought as a gift) 
Recipient UUID (blank unless bought as a gift)

Here’s an example of a line when the item was purchased as a gift.

"DavidThomas Scorbal","ad7b01b9-9b71-4beb-ba05-0c353ade5952","Big Red Box","2017-09-04 12:15:00","BlackFish","125","L","Ethan Renobaum","378d5dc6-9e5e-4107-baf4-922c0efda1f1"

The credit balance export looks like this:

"DavidThomas Scorbal","ad7b01b9-9b71-4beb-ba05-0c353ade5952","1200"
"Ethan Renobaum","378d5dc6-9e5e-4107-baf4-922c0efda1f1","215"

The columns, in order, are:

Avatar Name
Avatar UUID
Balance

 

 

Gift Card Sales

There’s no “sale” feature per-se for gift cards, but you can charge one number and award a different number of store credits – which can be advertised as a sale, or a bonus, or whatever you want.

This requires [E2V] Gift Card Vendor 3.4 to work. In the config notecard there is a line called

prices=

You can also add a line called

credits=

So for example:

prices=100
credits=200

would allow a customer to purchase a card for L$100, but receive L$200 when the card is redeemed.

Please note that the AllowCustomPrice setting cannot be used when using the “credits=” line.

Resetting Inventory Server Scripts

  1. Select one single product, either a vendor in-world or a redelivery item listed on your redelivery page.
  2. Locate which Storage Box on the Inventory Server contains this product.
  3. Copy the “bootstrap” script from that Storage Box into your inventory.
  4. Delete both scripts from the Storage Box
  5. Add the “bootstrap” script back into the Storage Box. (Yes, you just deleted it and then put it right back in.)
  6. Click the Inventory Server and select “Reset” – you’ll see floating text saying that a script is being delivered to a UUID. The Storage Box will now contain both scripts again.

Now test your product again.

If you need to do this to each Storage Box, here’s a shortcut. You only need 1 copy of the bootstrap script – they’re all the same. So just take one copy, then delete the scripts from all Storage Boxes, then add the bootstrap script back to each Storage Box, then reset the Server and the other script will be delivered to each of the boxes for you.

Copy scripts

The E2V-3 box contains two scripts to help copy the contents of one prim to another prim. The scripts are:

Copy prim contents - FROM HERE
Copy prim contents - TO HERE

We’ll call these the “FROM” script and the “TO” script.

To use the scripts:

  1. Drop the “FROM” script into the prim that contains the contents you want to copy.
  2. Drop the “TO” script into the prim that you want to copy the above contents into.
  3. Wait for a moment. The contents will be copied, and then both scripts will automatically remove themselves.
  4. Always complete one copy before doing another copy – even if you’re copying to/from the same prim(s) multiple times.

If you’re using these scripts to copy items into your E2V Inventory Server, remember that you will need to use “Edit Linked Parts” and put the TO script into one specific Storage Box at a time. You can place the TO script into the same prim over and over, to copy from several different objects into the same Storage Box, or you can put the TO script into a different Storage Box each time.

Working with others: Partnering vs Splitting

When you work with other people there are subtle, yet crucial differences between split profits and partnering. Here are the basic ideas…

First, whoever owns the vendor object gets 100% of the customer’s payment when that object is purchased. This is just how SL works, and has nothing to do with any vendor system. When someone pays money to an object you own, you get the money.

But, think about what else this means. If you own the vendor object, that means you also own the entire product itself. That’s because you can’t put something into your Inventory Server that you don’t own. So this means that even if someone helped you create all or part of your product, they would have given it to you at least with copy/transfer permissions, making you the final owner of the product.

The term “split” is really a bit of a misnomer. “Split” implies that you get part of the money coming in, but part of it is somehow diverted to someone else. This isn’t the case! You get 100% of the money. If you want someone else to also make money from this sale, then you have to pay them from your account. The split feature of a vendor system is intended to do this automatically for you, based on who you tell it to pay, and how much. As the sale is recorded, the system simply pays the split target the amount you specify, taking it from your account. That’s why splits require debit permissions.

Now, what if the person you’re working with doesn’t want to give you the item with copy/transfer perms, and wants to retain full ownership of the item they create, even though it’s selling in your store? You cannot place this item in your Inventory Server, and thus you cannot sell this item from a vendor object you own.

The owner of the item has to sell this item from their own vendor. But, if they do that, then the purchase will not show up under your redelivery terminal, any store credit earned will not be credited to the customer under your store, etc. All that sales data would go to the store of the owner of the vendor object.

This is where partnering comes in!

Partnering allows the vendor owner to say “I want sales of this item to be part of someone else’s store, instead of my store.” So whether a customer buys an item owned by you, or by your partner, the item still shows up your store’s redelivery page, any buyer’s rewards still affect their credit balance in your store, etc.

In version 4, partner mode can be applied to every vendor on a region, or only to specific vendors.

Events vs Main Stores

“How do I set up for an event, which is on a different region than my main store?”

I answer this question a lot, which is a sure indication that it’s confusing! There are big changes coming in Version 4, to simplify this (and a million other things). But for now, I’ll recap how things work in Version 3.

No Difference Between Events and Main Stores

This is the important thing to remember: there is no difference between your “main store” and an “event.” Here’s all the system cares about: regions. Any region where you want to have vendors will be set up the same as any other region.

Sometimes people get confused by the Inventory Server being on the same region as one of their stores. The Inventory Server can live on any region in SL, whether you have a store there or not. If you have a private home sim, your Inventory Server can live there. It’s the one special-case object in the system, because you only need one of them to cover the entire SL grid, and it does not matter what region you keep it on.

How to Set Up on Any Region

Here’s how you set up any region in SL to have your vendors on it (in the current version!)

  1. Rez a Store Controller, then a Transaction Relay, and then a Delivery Relay. Remember that only objects that come from the Release 9 folder will work.
  2. Now you can create vendors.

If you use Take in your viewer to grab copies of working vendors from one region to rez them on another region, it’s always a good idea to reset everything once you’re done rezzing vendors.

Can’t Spare The Prims?

If you can’t spare the 3 prims needed for the store support objects, there are other options.

I can spare 2 prims – If you place a boxed copy of the product inside every vendor prim, then you will no longer need the Delivery Relay.

I can’t spare any prims – Then you will need to use a script called the EventVendor, which you’ll find in your Release 9 folder. The EventVendor also requires that the boxed product be placed inside the vendor prim. It also has a different way of setting the vendor options. If you need to use this script, please shoot me an IM and I’ll help you get the options set correctly.

 

E2V Version 4

I’m going to begin publishing a few articles here and there about what to expect from the E2V system in version 4. These will include information about new features, and/or ways existing features and procedures will be changing. Here’s a few quickies for today…

Easy Updates – Keeping your system up to date will be easier than ever. Updates will be delivered to you automatically, and will (in all foreseeable cases) consist of a single box that you’ll just rez, click, and let it do its thing automatically.

Simpler Options Settings – The options settings on each vendor are going to return to version 2 style. For version 3 users, your existing vendors will be converted automatically for you, and you’ll find setting options to be much simpler going forward. For version 2 users, you’ll already be familiar with how to set options. This is to allow for more feature flexibility, and simpler instructions!

New 1-prim Controller object – There are several individual store support objects in version 3 that will be combined into a single Controller object for version 4. This means just one prim will be needed to run a store on any region.

More info coming in the future …