Give store credit from a customer event
Let a flow in your customer platform give a customer store credit in KNKTD OS, within limits you set, and tell them about it.
A customer event is one thing your customer platform can tell KNKTD OS, and what KNKTD OS does when it hears it. An event can give the customer store credit. Your platform's flow decides who qualifies and when. KNKTD OS checks the limits you set, gives the credit in your Shopify store, and can then tell the customer: with an event sent back to your flow, or with an email from KNKTD OS.
You manage events under Settings → Integrations, on your returns portal's page, in the Customer events tab.
Before you start
- Shopify is connected with store credit turned on. If the store was connected a long time ago, reconnect it so KNKTD OS can give credit.
- The workspace owner set the event credit limits. See Set the workspace limits. An event that gives credit cannot go live without them.
- You have the "Customer events: sending and rewards" permission, and you can manage integrations. An owner grants the permission under Settings → Roles. Owners and admins have it already.
Set the workspace limits
The workspace owner does this once. Under Customers → Rewards, open the ⋯ menu beside New programme and choose Event credit limits.
- Enter a Daily limit. It is the most that all events together give in 24 hours.
- Enter a Weekly limit, for 7 days. Left empty, it is five times the daily limit.
- Click Save limits.
Both limits are in your workspace currency. Only the owner can change them.
Add the credit to an event
- In the Customer events tab, click Add event, or edit an event.
- Click Add an action and choose Give store credit. It is always the first action of its event.
- Fill in the credit:
| Field | What it means |
|---|---|
| Amount | What one customer gets, in your workspace currency. From 1 to 50. |
| Expires | A number of days after the credit is given, or a fixed date. |
| How often a customer can get it | Once in their lifetime, once every few days, months or years, or every time the event arrives. |
| Daily limit for this event | The most this one event gives in 24 hours. |
| Weekly limit for this event | The most in 7 days. Left empty, it is five times the daily limit. |
- Tick I understand who can cause this credit.
- Save the event as a Draft first.
A customer who pays in another currency gets the amount converted at KNKTD OS's stored exchange rate, rounded up to a whole unit. So 10.00 can become 14.00 in another currency. Your limits count what is really given: the rounded amount, worth back in your workspace currency. That can be a little more than the amount you entered. No single credit is ever worth more than 50 in your workspace currency. When rounding up would pass 50, the credit is rounded down.
How the repeat rule counts
- Days count from the customer's last credit from this event.
- Months and years are calendar periods in your workspace time zone. "Once every year" means once per calendar year, so a birthday that arrives a day early next year is still paid.
- Every time has no cap of its own. Only your daily and weekly limits cap it.
The same call delivered twice never pays twice.
Tell the customer
KNKTD OS does not announce the credit by itself. Add one action after the credit to tell the customer. There are two choices. Use one of them, not both.
Send an event back
Your customer platform sends the message. Choose this when you want the message in your platform's own design and flows.
- Add Send an event back after the credit.
- Give the event a name, for example
abandoned-cart-credit-issued. - In your platform, build a flow that starts on that event and sends your message.
The event carries the customer's email and these values: amount, amount_text, currency and expires_on. It is
sent only after the credit was really given. If the credit was not given, nothing is sent.
Email the customer
KNKTD OS sends the email. Choose this when you want no flow to build in your platform.
- Add Email the customer after the credit. There is nothing to fill in.
- To change the email, click Edit email on the action. It opens Store credit added by event under Settings → Email notifications. Owners and admins can edit it. Other people do not see the link.
The email says how much was added and when it expires. It asks the customer to sign in to their account with the same email address to use the credit. It is sent only after the credit was really given, to the customer the credit went to.
- The email has a switch under Settings → Email notifications. While it is off, no email is sent and the event's row says so.
- Your own design is used only when your workspace sends from its own verified domain. Otherwise KNKTD's design is sent.
- The email has
{{amount}},{{amount_text}},{{currency}}and{{expires_on}}. Keep it about the credit. It is an account notice, not marketing. - An event sends at most 500 of these emails in 24 hours.
- No email is sent to a customer who was erased or who has no email address.
One notice per credit
A customer is told once about each credit. An event that gives credit can hold Send an event back or Email the customer, never both. When the customer was already told, a second notice is skipped, and Recent runs says The customer was already told about this credit.
If you save a credit with no action that tells the customer, KNKTD OS asks you to confirm that nobody will be told.
If the customer was not told
Sometimes a credit is given and its notice never leaves. For example, your platform refused the event, or the email was switched off. The Health card counts these as Credits given with no notice confirmed. A credit is counted 72 hours after it was given, for 30 days. A credit with a take-back that is pending or done is not counted.
The workspace owner can then send KNKTD's email by hand:
- On the event's row, open Recent runs.
- Find the call. On its credit line, click Send KNKTD's email instead.
- Click Send email.
The email is sent once. The button shows only when all of these are true:
- The credit was given in the last 30 days and no take-back was asked for it. A take-back that failed does not count.
- The customer was not told, and the event has finished running.
- Store credit added by event is switched on.
- The customer was not erased and has an email address.
When the button is not there, the owner sees one line under the credit that says why: the event is still running, the email is switched off, the customer was erased or has no email address, the credit is more than 30 days old, or a take-back was asked for the credit. Only the owner sees this line. There is no line when the customer was already told.
If the first notice got no answer, it may still have reached the customer. KNKTD OS warns you before you send, because the customer could then get two messages.
If the mail service gives no answer to this email, KNKTD OS does not send it again. The credit line then says the email was not confirmed, and the Health card keeps counting the credit. Tell the customer yourself if you need to be sure.
Once a take-back is asked for a credit, the credit gets no notice. This is true while Shopify has not confirmed the take-back yet, and after it is done. It is true for the event sent back, for the email and for this button. Recent runs then says A take-back was asked for this credit, so the customer is not told. If the customer was told before the take-back, Recent runs keeps saying they were told. A take-back that failed does not stop the notice.
Put the code in your platform
An event that gives store credit has a key of its own. Its channel's shared code does not start it.
- Only the workspace owner can see this key. The owner opens the ⋯ menu on the event's row, chooses Get the code and follows the steps. Until the event receives its first call, Get the code is also a button on the row.
- Anyone who can see the flow in your platform can read the key and cause credit. Your limits are the most that this can cost per day and per week.
- To stop an old key, the owner opens the ⋯ menu on the event's row, chooses Get the code and clicks Replace key. The old key stops at once, so put the new one in your platform right away.
If calls are refused
- A call that carries an old key, the channel's shared code, or no key is refused. Nothing is stored for it, so it is not in Recent runs.
- The event's row and the Health card then say Calls for this event are being refused. The Health card names the event and shows the time of the last refused call.
- The owner opens the ⋯ menu on the event's row, chooses Get the code, and pastes the code into the event's flow in your platform again. Other people are told that the owner does this.
- When a call is accepted after the last refused one, the line leaves the event's row. This can take about a minute. The Health card then says Calls have been accepted since, in grey, with the time of the last refused call.
- Every line goes away 24 hours after the last refused call.
If two flows send the same event, check both. One accepted call makes the row quiet even when the other flow still uses an old key. The next refused call brings the line back.
An event that is switched off shows no such line. An event without a key of its own does not either: a wrong key on its channel shows as Last problem on the Health card.
Test it, then go live
While the event is a Draft, a call gives nothing. Open Recent runs on the event's row to see what would have happened: the amount that would be added, or the reason it would be skipped.
When the draft runs look right, set the event Live. From then on a call gives real store credit as soon as it arrives. The credit usually appears on the customer's balance within minutes.
When no credit is given
Recent runs says why. The most common reasons:
| What you see | What to do |
|---|---|
| The customer already got this credit | The repeat rule refused it. Nothing to do. |
| A daily or weekly limit was reached | The credit was not reserved. Raise the limit if this is expected. |
| No customer was found for this call | The email is not a customer in KNKTD OS. KNKTD OS never creates one. |
| The customer has no store account | The customer exists but has no Shopify account to hold credit. |
| More than one customer has this address | Merge the duplicates in Shopify. |
| No exchange rate for the customer's currency | KNKTD OS never guesses a rate, so nothing is given. |
| Event credits are paused | The workspace owner resumes them under Customers → Rewards. |
| The workspace limits for event credit are not set | The workspace owner sets them. |
A credit that says Waiting for room under a daily or weekly limit was reserved and is given when the limit allows.
What Recent runs and Health say
Recent runs shows each call of an event. A call that gave credit has a credit line, and a line for its notice.
| Credit line | What it means |
|---|---|
| Credit reserved | The credit is set aside. It is issued within minutes. |
| Credit reserved, with Waiting for room under a daily or weekly limit | It is given when the limit allows. |
| Credit reserved, with Event credits are paused | It waits until the workspace owner resumes event credits. |
| Credit reserved, and it cannot be given | It is more than a limit allows. The line says what to do. |
| Credit needs the owner | Shopify did not confirm it. The workspace owner decides whether it was given. |
| Credit issued | The credit is on the customer's balance. |
| Credit being taken back | A take-back was asked for and Shopify has not confirmed it yet. |
| Credit taken back | The credit, or the part that was still there, is off the balance. |
| Credit not given | The line says why. |
| Credit cancelled | It was cancelled before it was given. The line says why. |
| Notice line | What it means |
|---|---|
| Accepted by your platform | The event was sent back and your platform took it. Your platform does not report whether its flow ran. |
| Email sent to the customer. | KNKTD's email was accepted by the mail service. |
| The customer was already told about this credit | A second notice was skipped. |
| A take-back was asked for this credit, so the customer is not told | A take-back was asked for before the notice went out. It may still be waiting for Shopify, or it may be done. |
| The store credit was not given | There was no credit to tell the customer about. |
| KNKTD's email for this credit was not confirmed. The customer may not have been told. It is not sent again. | The owner sent KNKTD's email by hand and the mail service gave no answer. |
The Health card has these lines when an event gives store credit:
| Health line | What it means |
|---|---|
| Event credit, last 24 hours and waiting | What all events gave in 24 hours, plus every credit still waiting, against the workspace daily limit. |
| Credits that need you | Credits Shopify did not confirm. Review opens them. |
| Event credits | On or Paused. |
| Credits waiting for limit room | Reserved credits that are given when a limit allows. |
| Credits the limits can never fit | Reserved credits that are more than a limit. Raise the limit, or pause and cancel them. |
| Credits given with no notice confirmed | See If the customer was not told. |
| Calls for (the event) are being refused | See If calls are refused. |
| Calls for (the event) were refused, with Calls have been accepted since | The flow works again. Nothing to do. |
The last five lines show only when there is something to report.
Pause everything
Under Customers → Rewards, open the ⋯ menu and choose Event credit limits. There an owner or an admin can click Pause all event rewards. No event gives credit while paused, and the workspace owners are told.
Only the workspace owner can Resume. If credits were waiting, the owner chooses to issue them or to cancel them. A cancelled credit is not given, and its customer is not told.
Take a credit back
Under Customers → Rewards, in Payouts, the workspace owner can click Take back on a credit an event gave.
- KNKTD OS takes at most what is still on the customer's balance. It never puts a balance below zero.
- The customer is not emailed.
- If the customer was not told about the credit yet, they are not told now.
- A credit can be taken back once.
A credit needs your decision
Sometimes Shopify does not confirm a credit. KNKTD OS never sends it again by itself. The Health card shows Credits that need you, and the workspace owner decides under Customers → Rewards whether it was given.
Where the credit shows up
- Customers → Rewards lists each event's credit as a Customer event, with its amount and rule. You edit it in the event, not there.
- The customer's store credit history names the event that gave the credit.
- Reports show it as Event credit, apart from order cashback.
- Event credit never earns cashback.
