CasperVend 2/EasyVend: Difference between revisions

From CasperTech Wiki
Jump to navigation Jump to search
Line 61: Line 61:
:# Look for the EasyVend box, rez and unpack that
:# Look for the EasyVend box, rez and unpack that


= '''<span style="color:#00528c">Permissions</span>''' =
= '''<span style="color:#00528c">Debit Permissions</span>''' =
The E2V system did not ask for debit permissions from vendors (because that was handled by the Payment Server).
 
However, EasyVend does *NOT* use the Payment Server, so '''all''' EasyVend vendors ask for debit permissions when newly created, updated, or hard reset (right-click > edit > "reset scripts in selection").
 
The reason you will be getting debit permissions windows is because the new script does NOT remember any permissions that may (or may not have been) given to the old scripts. This is '''required''' by LSL. The same thing happens when an existing script is hard-reset (Such as if you're using Edit > Reset scripts). More information on '''[[Debit_Permissions | debit permissions is here.]]'''


= '''<span style="color:#00528c">Sales Data Migration from E2V to CasperVend</span>''' =
= '''<span style="color:#00528c">Sales Data Migration from E2V to CasperVend</span>''' =

Revision as of 16:04, 3 December 2020

Most CT staff and other users *don't* use EasyVend on a normal basis! Be sure to file a support ticket AND specify that you're using EasyVend.

Introduction

EasyVend is an expansion pack for CasperVend that allows the easy migration of users from the now-defunct E2V vending system over to CasperVend.

Purpose of EasyVend

This expansion was created to assist people migrating in to CasperVend from E2V, another vendor system which was cut off and shut down in May 2018.

If you were NOT using E2V before it was shut down, you will find this expansion VERY frustrating, and VERY time consuming - you might want to start with the normal Quick Start instead!

What's in the box?

EasyVend Features

  • Drop-in replacement for E2V vendor scripts
  • Drop-in replacement for E2V store controller to support profit splits, sales, price groups
  • Drop-in replacement for E2V inventory server for remote delivery
  • Obeys E2V naming rules for item matching
  • Supports DropBox delivery, local vendor delivery and folder delivery
  • Automatically creates products in the CasperVend system
  • Web management not necessary with EasyVend
  • Splits and profit Sharing ARE supported

E2V Items NOT Used by EasyVend

You will NOT need to rez or use any of these items from the E2V vendor pack when converting to EasyVend:

  • Delivery Relay
  • Payments Object
  • Transaction Relay

EasyVend Limitations

  • NOT SUPPORTED: E2V's "partner" sharing feature (because you cannot share inventory servers in CasperVend)
  • NOT SUPPORTED: Group discounts (that's only supported with the full CasperVend)
  • CV Gift Cards: Accepted - will work with local/folder delivery as of version EasyVend v2.01
  • The EasyVend does not display textures - if you want automatic texture management use the full CasperVend
  • You can't manage what displays on the vendor from the web
  • You can't manage profit shares or store credit awards from the web
  • If you use local vendor or folder deliveries, customers will be unable to claim redeliveries using the automatically created products. However, you can edit the product on the web interface and designate a packaged version (and set "copy" perms to allow redelivery) for that product to use for redelivery.
  • Like E2V itself, EasyVend cannot be used as affiliate vendors

Where are the EasyVend Scripts?

Redeliver your PAID CasperVend pack - either "Premium" or "Fat Pack". EasyVend is NOT in the free commission vendors!

FatPack


  1. Rez your fresh FatPack crate
  2. Unpack your FatPack into your inventory
  3. Look for the "Premium Vendors" crate in inventory
  4. Rez the "Premium Vendors" crate
  5. Unpack to inventory
  6. Look for the EasyVend box, rez and unpack that

Premium Vendors


  1. Rez the fresh "Premium Vendors" crate
  2. Unpack to inventory
  3. Look for the EasyVend box, rez and unpack that

Debit Permissions

The E2V system did not ask for debit permissions from vendors (because that was handled by the Payment Server).

However, EasyVend does *NOT* use the Payment Server, so all EasyVend vendors ask for debit permissions when newly created, updated, or hard reset (right-click > edit > "reset scripts in selection").

The reason you will be getting debit permissions windows is because the new script does NOT remember any permissions that may (or may not have been) given to the old scripts. This is required by LSL. The same thing happens when an existing script is hard-reset (Such as if you're using Edit > Reset scripts). More information on debit permissions is here.

Sales Data Migration from E2V to CasperVend

Self-Hosted Migration

If you are a self-hosted E2V customer, and want to export your data, go here for information and instructions.

E2-Designs Hosted

To export your E2V sales data, provided the system is still up, you need to log in to E2V and go here then select what month sales data to export, and save it. Same with your credit history.

Convert Existing E2V Vendors to EasyVend

Migration Options

You may choose to replace the scripts in your existing vendors, either manually, or with the new MigrationBee

Products Must Be Ready

Products must be ready - as in, they must be packaged and in the dropbox, and/or in the vendors BEFORE resetting / changing the scripts to EasyVend. If the product is added after, the vendor will not work. (So reset them again, if you happened to add the products last.)

Debit Permissions

Manually Converting E2V Vendors

Using Migration Bee

Naming Suffix Rules

Name Matching

About the Description Field

Delivery Methods After Conversion

Redeliverable Delivery

Non-Redeliverable Delivery

Vendor Delivery - Packaged


Vendor Delivery - Folder


Sales & Discounts

Sales & Pricing

Discounts & Credits

Gifting

Gift Cards

Vending At Events

Creating New EasyVend Vendors

Converting from EasyVend to regular CasperVend

Troubleshooting