Developer notes
This page explains what the finished system is designed to do, how the customer experience works, and why each part matters to the business.
Products, prices, availability, pickup details, and trust information in one place.
Payment, customer details, item choices, pickup selection, and notes stay together.
Email capture, coupons, customer records, and sales information support repeat business.
The business owns the accounts and can manage routine changes through its own tools.
Look ready for business
Give customers one clear place to see the food, understand the choices, and feel ready to order.
The business gets one clear home for its name, visual identity, photos, story, menu, pickup information, and customer contact paths.
Why it helps: Customers can understand what is available and trust that they are ordering from the right business.
Customers can view meals, breads, pantry items, drinks, and other categories. Each item can include a photo, description, price, serving information, and availability.
Why it helps: People can make a decision without sending messages for basic information first.
An item can have one option or several. Each size, serving amount, or format displays its own price and availability.
Why it helps: Customers know exactly what they are getting and how much it costs before checkout.
The business can choose which products appear most prominently and can highlight new items, popular items, holiday offerings, or weekly specials.
Why it helps: The homepage can direct attention toward the products the business most wants to sell.
Products and sizes can have a regular price and a sale price. Customers see the original price, current price, and savings clearly.
Why it helps: Promotions can move extra inventory, introduce a new product, or encourage customers to order sooner.
Take orders without the chase
Make each order clear, paid, scheduled, and easy to find when it is time to prepare the food.
Customers pay while placing the order. An unpaid cart is not treated as a confirmed order.
Why it helps: The business does not buy ingredients or prepare food for someone who may never complete the purchase.
Customers choose from the pickup dates and time windows the business makes available.
Why it helps: The kitchen knows when each customer is coming and can plan production around real orders.
The business chooses when ordering is open. Dates can be added, closed, paused, or limited based on capacity.
Why it helps: The website works around the kitchen schedule instead of forcing the business to appear open every day.
Products, order quantities, or pickup spaces can be limited. Items can show as unavailable when the limit is reached.
Why it helps: The kitchen only accepts the amount of work it can complete well.
Products can remain saved when they are not currently available and can be turned back on later without being recreated.
Why it helps: Seasonal dishes, holiday menus, and occasional specials are easy to bring back.
Customers receive a confirmation after ordering and a reminder before pickup.
Why it helps: Customers are less likely to forget the order, arrive at the wrong time, or ask for information the system already has.
The business receives a notification when a paid order enters the system.
Why it helps: The owner knows what needs to be prepared without constantly checking the website.
Orders stay together with the customer name, items, variants, pickup time, payment status, contact information, and notes.
Why it helps: The business no longer has to reconstruct orders from social messages, text conversations, calls, and handwritten notes.
Bring customers back
Make it easier for people to order again, hear about the next menu, and place larger requests.
Customers can provide the event date, guest count, type of gathering, and other details for a custom proposal.
Why it helps: The business can pursue larger orders without forcing every request through the standard menu checkout.
The owner can create discount codes for special offers, first-time customers, repeat customers, or specific products.
Why it helps: Coupons create a direct reason to place an order now or return for another one.
Customers can sign up to hear when ordering opens, a new menu is posted, or a special product becomes available.
Why it helps: The business can bring customers back directly instead of waiting for them to notice another social-media post.
The system can show which products sell, which offers convert, when customers return, and what order patterns are developing.
Why it helps: The owner can make better decisions about future menus, quantities, ingredient spending, and promotions.
Stay in control
Change the business when needed, whether the kitchen is taking a quiet break or preparing for more demand.
The owner can update products, photos, prices, sizes, sale prices, featured items, pickup dates, availability, and business information without changing website code.
Why it helps: Routine updates do not require a developer, while the design and customer flow remain protected.
The menu, ordering flow, and management controls are designed around the devices the owner and customers actually use.
Why it helps: The owner can handle common updates from a phone, and customers can order wherever they happen to be.
The website, payment account, customer list, order records, analytics, content, and connected services remain under accounts the business controls.
Why it helps: The business is not trapped inside a platform or dependent on one developer to continue operating.
The owner can pause orders, add pickup days, introduce more products, expand fulfillment, or connect additional customer tools as the business changes.
Why it helps: The same foundation can support occasional weekend sales, busy seasonal runs, or a larger full-time operation.
The simple idea
Sol & Sage stays in control of what it sells, when it sells, how customers order, and the information created by those sales. The Site and Product Manager handles routine updates; the optional Care Plan is available for technical work outside those controls.