MicroSky Food online ordering is the site with your name on it. A guest builds a meal, pays, and sends a ticket to your kitchen. They are not in a marketplace list beside the restaurant down the street. The domain, the photos, the menu, and the customer list stay with you.
This post is the shift version of that site: who it helps, what the guest taps, and what the counter sees. The feature list is on online ordering. Plan math is on pricing. Changes since go-live are on the release notes.
Who it helps on a normal day
It helps an independent restaurant or pizzeria whose regulars already know the name, whether they are on the couch or outside in the car. The cook still needs a ticket that matches the window: a size, toppings, and a note on their own lines.
It also helps the person on the station who is not the owner. Staff accounts have roles, so a manager or the counter can run the shift without your password. That login is in restaurant admin. The dining-room register can stay. These orders run beside it.
You set the delivery zone and the charge. The software does not send drivers, and it does not go find new guests for you.
How a guest places the order
The guest opens your site on a phone. It runs on your domain, with your branding, your photos, and your menu. The layout is mobile-first. On a phone, Add to cart sits under the quantity picker.
The onboarding wizard can scan a site you already have and import menu items, prices, modifiers, and images, then launch the storefront and admin on your domain. Read that import before you share the link. How it works is the path: profile, menu, hours, delivery zones, and billing. Most restaurants are set up the same day. A wrong topping still needs a human pass.
The menu, the cart, and the payment
Items sit in categories guests can browse or search. Items and categories are unlimited. Each item can have a photo, a description, and a price you control. Sizes, toppings, and other modifiers can each carry a price. Required choices show before optional ones, and you can turn off an add-on that does not belong on an item.
A live cart follows the guest with the item count and a running subtotal. Checkout is the short path from that cart to payment, and a paid order gets a confirmation. Signed-in guests can pay with a saved card. You can turn on pay at pickup if the counter works that way.
Bring a Stripe token, connect Authorize.net, or sign up with Electronic Payments. Cards are encrypted. Cash on delivery can cover you while a merchant application is processing. The guest should see a clear receipt. The kitchen should see a paid ticket.
Pickup, delivery, and the hours on the door
Offer pickup, delivery, or both. Pickup includes a ready time. Delivery uses the radius and zones you set, down to the mile, and the charge you choose. A published example is a zone with no delivery charge inside 4 miles. That zone is your setting. You can also set a delivery minimum. If you do not drive past a certain road, say so before the guest pays.
Ordering opens and closes with your posted hours. After close, the button steps back so guests can see you are closed. You can schedule a closing, hide a category when its hours end, and use a late-night menu for extended pickup. When an item sells out, 86 it. A price change or a special updates the storefront. The closer needs a staff login that can edit the menu.
The second order is the saved one
Guests can create an account, save an order, and place it again. Loyalty points accrue on storefront purchases on every plan, and you set what they are worth. Someone who makes an account at checkout keeps the points from that order. The customer list stays yours.
Email and SMS campaigns to that list are Growth Plus, not Standard. A shopper who leaves checkout can get an optional reminder, and a failed payment can get one reminder.
What the kitchen sees
New orders appear in admin from new, to preparing, to ready, to delivered. The day's pickups and deliveries sit together. You can cancel an order that will not be made, email the team when one comes in, and see who is still in checkout. Reports count completed, paid orders in your time zone.
Print on the receipt printer you already trust, or add the $500 hardware package: a mini PC print server and a receipt printer. Admin runs in the browser on a tablet or computer you have. A tablet can be provided. No new POS hardware is required.
Place one paid test on your site, or start from the live demo, and read the ticket. If the cook has to call the front for the size, the modifiers are not done.
The phone uses the same menu
Some guests will still call. Sky AI answers inbound calls, takes pickup or delivery from the published menu, collects card payment on a PCI-safe keypad, and prints the paid ticket with web orders. There is no per-minute fee, and it does not hear the full card number. It is not in the signup wizard. Turn it on in Admin under Integrations after a web ticket looks right.
Where the link goes, and what it costs
Put the link on the box, the window, the bio, and the order link on your Google Business Profile. Standard includes that listing link. It should open your site. Tap it from a phone that is not logged into admin. Every plan includes a title, a description, canonical URLs, JSON-LD, a sitemap, and headings on static-generated pages, with global edge delivery.
Standard is $249 per month plus 5% of net sales. Growth is $499 per month plus 7%, after 3 months on Standard, with a branded iOS app, a website redesign, push, and monthly work on 5 keywords. Growth Plus is $999 per month plus 10%, with email, SMS, and 10 keywords. A 30-day free trial does not skip those 3 months. There is no long-term contract. See pricing.
Third-party marketplaces often charge 15 to 30% of the order. MicroSky Food still has a monthly price and a percent of net sales. Guests are on your site, and the list stays yours. Restaurants already on the platform are on the clients page. Questions go through contact. Start 30 Day Free Trial. Call (888) 960-1359.