How to Create Gift Vouchers


Simple implementation of gift vouchers (selling and redeeming) is not a feature of the OFN platform at present, although it is something we hope to introduce in the future.

In the meantime it is possible to use tags and tag rules to create vouchers. The process is described below. Vouchers are always popular around Christmas and other seasonal events and owing to the complexity of issuing them it may be worth considering only offering vouchers at specific times of year.

An alternative 'gift' option which your enterprise may like to consider is to allow a customer (the gifter) to purchase a subscription (regular order) for a friend or family member (giftee). For example the gifter could arrange for the giftee to receive their favourite handmade, local bread to be delivered to them (paid for by gifter), from your food enterprise, every week for a month.

This would have the extra advantage for the gifter that the cost of the gift would be spread weekly and not a lump payment: cash flow for everyone is tight at Christmas and other seasonal periods!


This is a multi-step process

Step One

Create a product listing for vouchers. We suggest that you keep it simple ie. having a maximum of three different denominations of voucher only (£10, £20, £50). Remember:

  • To include instructions to the customer on how they can redeem their voucher later (they will need to ask the recipient of the voucher to email your enterprise with their voucher ID number (see step 2) and email address (step 5) with which they have set up an OFN account.)

  • That enterprise fees are included in the price of the voucher. The person who redeems the voucher will also have the enterprise fee added onto the products they purchase (ie. fees will be collected twice). The extra enterprise fee may be necessary to cover the added overheads of admin work, processing gift vouchers. Alternatively the product price can be adjusted so that the customer facing price (product price + fee) is the voucher’s value.

Step Two

Email a voucher to the customer or print off a paper one. Give each voucher a unique number (perhaps use their OFN order number with post fix of a, b, c etc if more than one voucher purchased in the same transaction).


This voucher was made using the free online software Canva.

Step Three

Make a spreadsheet to record sales and keep track of claims: name of customer (gifter), amount, date of issue, order number/voucher ID number, name of recipient (giftee), credit remaining.

Gifter email address

Value of Voucher

Date purchased

Voucher ID number

Giftee email address

Credit remaining

… Joe Bloggs





… Mr Baker


Step Four

Customer who bought the voucher (gifter) gives it to a friend or family member at Christmas (giftee). For the giftee to redeem their voucher they need to contact your hub/shop informing you of:

  • The email address associated with their OFN account (for step 5)

  • Their unique voucher ID number (for you to keep track of vouchers issued and redeemed).

Step Five

Add the giftee to your enterprise Customer list if they have not purchased from the shop in the past. If they have brought before then they will appear on the list already.

Add a unique tag next to the customer’s name. Perhaps use initials-underscore-last four digits of the voucher ID number (set up a consistent way of doing this).

Step Six

Set up a NEW payment method which will be UNIQUE to this customer (the giftee). Payment Methods can be found by visiting Enterprises -> Settings -> Payment Methods +New Payment Method.

Description- use the description box to explain to the customer the value of the voucher they have received from their friend/family, that any balance on their order will need to be made up by cash or BACS (provide bank details on how to do this) if necessary. It is also worth explaining any terms and conditions- for example that the voucher is single use (ie. once the value has been claimed then if they use the voucher again immediately the 2nd order will be cancelled or full payment will be required) and expiry date for the voucher. Display = Both Checkout and Backoffice Active = yes Add tag to payment method (same as used for the customer). Provider- cash (if the customer spends more than the value of their voucher then they will need to pay the remainder by cash or BACS)

Do not use an automated payment provider (Stripe or PayPal) here as this will result in a payment being made from your enterprise into the giftee's bank account if they spend less than the voucher value.

Fee Calculator: Flat Rate Amount: enter the value of their voucher prefixed by a negative sign.

Step Seven

Set up a Tag rule (visit Enterprises -> Settings -> Tag Rules):

Default: Payment Methods tagged initials_digits are not visible Rule: for customers tagged initials_digits payment methods tagged initials_digits are visible.

Customer (giftee) uses voucher and exceeds the value of credit remaining:

  • Delete their unique payment method, tag rule and tag associated with customer’s (giftee’s) name.

  • Obtain the balance of their order by cash payment or BACS

Customer (giftee) uses voucher but doesn’t spend its entire value:

Edit their unique payment method to adjust the ‘amount’ under Fee Calculator to their remaining voucher balance (eg. if the voucher’s original value was £20, they spent £15 then the original amount would be -20 and the amount after their first transaction would need to be edited to -5)

Things to note:

  • If a customer (giftee) makes a second purchase before you have had a chance to update their remaining credit or remove the unique payment option (if all their credit has been used up) then they will have the option to claim the voucher’s value twice. This relies on the customer being honest and not doing so. This should be mentioned on the voucher and in the description of their payment method (step 6). As an enterprise you could cancel orders if a voucher is redeemed inappropriately- always good to notify the customer (giftee) first though!

  • It is a good policy with vouchers to set an expiry date (say 12 months).

Last updated