docs
/
AI skills

Phone order for a customer

Take an order for a customer on their behalf, unpaid or paid outside the shop. Find or create the customer, put the products on an invoice saved as a draft, turn it into an order in their history, and send the invoice only when told.

Staff don't key orders into the Orders screen directly. In Appmint, a staff order goes through the invoice. The invoice holds the customer and the lines, and Create Order turns it into a real order that belongs to the customer. Saving an invoice never contacts the customer. Only Send does.

Ask first

  • Who is the customer? Name plus an email or phone. Look them up before creating anyone.
  • What are they ordering? Each product, the variant (size, colour) and the quantity.
  • Where does it go? The delivery address, if it will be shipped.
  • Payment. Unpaid (they pay later), or already paid outside the shop (cash, cheque, bank transfer). If it was paid, ask how and the reference.
  • Should the invoice be sent to them? By email, text or both. Ask, and never assume.

Steps

1. Customers & Benefits: find the customer

Search customer by email, then by phone. If one is found, use them.

If none is found, don't create them separately: the invoice save in step 3 finds or creates the customer from customerEmail / customerPhone / customerName. This creates a plain customer record with no password and no welcome email.

Hands on: the customer's email (and sk, if found). Check: if found, open the customer (/customers-benefits?openId=<sk>) and confirm it is the right person. If two records could be them, ask which one.

2. Products: the lines

Find each product (sf_product) by name or SKU. For a product with variants, use the variant's own SKU and price from variations[], not the parent's.

Hands on: for each line, name, sku, quantity and price. Check: every product exists and is not draft or archived. If a product isn't in the catalogue, ask before adding a free-text line.

3. Invoices: the draft

Real action: POST storefront/invoices/save with:

  • customerName, customerEmail and/or customerPhone;
  • products: [{ name, sku, quantity, price }];
  • shippingAddress, if it ships;
  • status: 'draft'.

The save numbers the invoice, adds up the totals, attaches the customer (creating them if needed) and dates it. It does not email anyone.

Hands on: the invoice's sk and number. Check: open it (/invoice?openId=<sk>). The customer, the lines and the total match what the person said. Read the total back to them.

4. Orders: turn the invoice into an order

On screen: in the invoice, More → Create Order. Real action: POST storefront/invoices/<invoice sk>/create-order.

This creates the order (sf_order) with:

  • the lines;
  • invoiceNumber set to the invoice;
  • placedVia: 'invoice' and placedBy (the staff member);
  • the customer as its owner, so the order appears in their order history.

The status is new when unpaid, and paid when the invoice was already paid. The invoice gets the order number back, and converting it a second time is refused.

Converting does not take stock off. Stock kept in Inventory leaves when the order ships or is completed, as for a web order. A product that keeps only its own stock number (no Inventory rows) is not counted down for an order made from an invoice: if that matters, tell the person to change it. See Stock levels.

Hands on: the order's sk and number. Check: open the order (/order?openId=<order sk>). The lines and the customer are right. The customer's 360 view (/customers-benefits?openId=<customer sk>&recordTab=360) lists the order.

5. Payment (only if it was paid outside the shop)

Stop: this records money and emails the customer a payment confirmation. Confirm the amount and method first.

Real action: POST storefront/invoices/<sk>/mark-paid with { method, ref, amount }. Do this before step 4, so the order is created as paid.

Card payments are taken by a person on the invoice's Take Payment screen, never by the AI.

6. Send the invoice (only when told)

Stop: sending emails or texts the customer the invoice and a pay link, and books the sale in the accounts. Show the recipient and the total, and wait for yes.

Real action: POST storefront/invoices/<sk>/send with { channels: ['email'] | ['sms'] | both, emails?, phones? }. The invoice becomes sent.

When it's done

Tell the person:

  • the customer (found or newly created);
  • the invoice number and total, and whether it was sent;
  • the order number and its status (unpaid / paid).

Then say that the order is in the customer's history. Open the order on its own screen.