Case history
The checkout completes now, and the wine reaches a door inside Mexico. Behind the winery, the rooms and the dining room, one system is built and open to walk through.
Built to hold water
Photographs of En'kanto. The system described in these captions is built and not yet in service there.
BasisNo En'kanto revenue figure is published here, and no result from the system's use, because it is not in service there yet. The counts of the build on 9 September 2026 are: three modules, the nineteen screens named here in lists of five, five and nine, ten staff positions its own route table defines, and the four homepages we unpublished.
En'kanto sits in San Antonio de las Minas: a boutique winery, rooms for people who want to wake up in the Valle, and a restaurant. Three lines, one place.
Online, the store existed in name only: products with no price, no way to ship, five homepages competing for the same visitor. The order went on a pad and the bookings arrived in as many places as there were channels.
Real products with a price, a weight and an image, and a checkout that completes.
Illustrative card, invented product.
One address for the whole business.
The duplicates came down, one page stands for the wine, the stays and the restaurant, and search reads it the way a visitor does.
Paid the way people here pay.
Card and cash both reach a placed order, so the checkout stops being where a sale dies.
A bottle reaches a door inside Mexico.
A domestic carrier and packaging that meets the rules. Selling across the border as a Mexican winery is outside what the law allows, so guests from the north carry wine home under the personal allowance, and the store says so.
One store, read whole in two languages.
English and Spanish on one foundation, so a guest from the Valle and one from the north meet the same business.
Three operations shared a property and no shared record. We built the one they share: nineteen screens, a set per area, so each part works from its own.
01Produccion
The vineyard and its blocks, the season and the harvest window, pick dates and lab analysis by lot, fermentation by tank, and the barrel room card by card.
Screens
02Restaurante
Written once at the table, timed on the kitchen screen, seated from a table map, and closed on a summary and a cash cut with the difference.
Screens
03Hospedaje
Every channel in one calendar, the day's arrivals and departures, occupancy and revenue by channel, a guest record that outlives the booking, and housekeeping from a phone.
Screens
It mirrors the channels. It does not write to them.
Airbnb publishes no open interface for a host, so the calendar reads the iCal feeds, which refresh in hours. A date blocked here stays open there, and the screen says so.
It reads OpenTable. It does not scrape it.
Table bookings live in OpenTable, open to approved partners and to nobody else. Until that account is connected, the booking is taken by hand and reconciled against the export on guest and time, so one stays one.
A room bill adds up the restaurant's charges. It never writes one.
The front desk only reads them: creating or changing a charge belongs to the restaurant. A charge with no amount shows as pending and stays out of the total, and an example is labelled as one.
It is built. It is not yet in service at En'kanto.
Everything here is merged and running. Putting it into the property's daily work is the next phase, and until then we claim nothing about what it changed.
It runs as a public demonstration under a fictional name, assembled from a whitelist that leaves En'kanto's own data files out of the deployment. Open a module, pick any of the ten positions, walk its screens.
Open the demoIllustrative data under a fictional name. Nothing there belongs to a client.
The sale completes.
A price, a weight, a way to ship, and a checkout that ends in a placed order.
The order is written once.
From the phone at the table to the cash cut, with nobody copying it out again.
The system is yours.
The code, the data and the keys stay with the property.
Ten business days on your store, your site and your operation, and a written memo at the end.
Free. No retainer, no obligation. If the memo shows work worth doing, we propose the build and you decide.