Watch your game network's deliveries from the staff console

If your game network delivers what your store sells, as Connect your game network to your storefront sets up, three pages of the staff console watch it. "Deliveries", /staff/network/deliveries, lists every purchase your network delivers and says whether it reached the game. "Players", /staff/network/players, finds a player by name with everything bought for them. "Network status", /staff/network, says when your network last reported.

The pages sit under "Network" in the console's sidebar, on the brands whose console has them.

• Sell what the network delivers as "Standalone" products. The pages list only purchases of those products.
• Any member can read the three pages. Sending a purchase again needs Tier 2 support or above. Recording a delivery by hand needs Tier 3 support or above, because it tells the customer the purchase arrived.

1. Open "Deliveries". It opens on "Need attention": paid purchases whose delivery failed, and paid purchases your network has not confirmed within 10 minutes of the last change.
2. The tiles count "Need attention", "Failed", "Waiting", "Not reported" and "Delivered in 24 hours". Select a tile to list what it counts.
3. Search by part of the player's name, part of the customer's email address, or the purchase number. Pick a product to list only its purchases.

Every filter is in the page's address, so you can send a colleague the list you are looking at.

Use this when the network failed to deliver, for example because the player was offline or a plugin was down, and it can try again.

1. Open the purchase from "Deliveries" or from a player.
2. Select "Send again", write why, and confirm.

Coritan forgets the delivery the network recorded and moves the purchase to the end of the purchases your network reads. Your network then reads it as one it has not delivered. Only an active purchase can be sent again.

Use this when the purchase was given some other way, for example by a moderator in game, or when it cannot be delivered.

1. Open the purchase.
2. Open the actions menu (⋯) and select "Record as delivered" or "Record as failed".
3. Write what the customer should read beside it, if anything, and why you are recording it by hand. Confirm.

The customer's account shows the delivery as your network would, and the history says a member of staff recorded it.

The purchase page lists every delivery your network recorded and every time staff sent the purchase again or recorded it by hand, newest first, with the reason given. "Player" shows the name and edition the customer ordered for, and when your network last saw that player.

1. Open "Players" and type the start of the player's name. For a player whose name has a prefix, such as -Alex, type the prefix too.
2. Each player shows their edition, when your network last saw them, and their purchases. A player your network never reported shows "Not seen in game": the name came only from an order.

"Network status" shows when your network last sent its status, market, leaderboards and players. A report older than 5 minutes is "Stale". The page also shows when the network last recorded a delivery, and the active API keys that can reach the purchases, with when each was last used. It never shows a key.

A stale status on a running network usually means its program stopped sending, or its key was revoked. Troubleshooting in Connect your game network covers both.

On "Alerts", add a rule of the kind "Purchases not delivered". It fires when the number of purchases that need attention reaches the number you set, and links to the Deliveries list. Set up alerts for your team explains rules, channels and cooldowns. The desk also shows a "Deliveries" tile when any purchase needs attention.

You can see which purchases reached the game, fix the ones that did not, and know within minutes when your network stops reporting.

• Sending again and recording by hand are limited to 60 an hour for each member.
• A reason is 3 to 300 characters. What the customer reads beside a delivery is at most 300 characters.
• "Players" finds names by their start, and shows at most 50 players.

"A purchase sent again comes back as failed." Your network tried and failed again. Open the purchase and read the latest entry in its history for the network's reason.

"Send again answers that the purchase cannot be sent." It is cancelled, suspended or ended. Only an active purchase is delivered.

"The pages are empty." Your brand sells no standalone products, or your network has not been connected. See Connect your game network to your storefront.

• Connect your game network to your storefront
• Set up alerts for your team
• Look after customers in the staff console