Build · Menu Import
LimeOrigin reads the same menu PDF you send to your printer, compares it with what your website says, and shows you the differences — the new dishes, the ones that have gone, the prices that moved. You approve what you want and leave the rest.
The new menu came back from the printer a month ago. The website still has last season's dishes and the old prices, because nobody has an evening free to retype forty lines.
Menus made on a computer — designed, exported or printed to PDF — are read straight from the file. If it cannot read one, it says so plainly instead of guessing, and the PDF menu on your website carries on working exactly as before.
You are shown what is different: dishes added, dishes no longer there, prices that moved, wording that changed. When a menu has been redesigned but the food is the same, it tells you nothing meaningful changed — rather than handing you forty differences that are really one new typeface.
“Pan-fried sea bass” becoming “Sea bass, pan-fried” is one dish with new wording, not one dish gone and another arrived. It stays in place and keeps its photograph, its position and its history.
Where it cannot tell which of your dishes a line refers to, it asks you rather than deciding. A question you answer in a second is worth more than a confident answer that is wrong.
Confirm once that the “House Burger” on the printed menu is your “Classic Burger”, and it knows next time. What you confirm is kept for your website and never pooled with anybody else's.
A changed allergen or a changed price is not the same as a changed comma, and it is not treated as one. Accept the routine wording changes together if you like — the prices and the allergens still come to you one at a time.
Every proposed change is yours to accept or reject. What you do not approve is not touched, and the menu on your website does not move until you apply what you decided.
Changed your mind after applying one? Put the menu back exactly as it was immediately before it, in one step.
“Last confirmed against a document seven months ago.” “A newer document has been read and nobody has reviewed it.” Real facts about what actually happened, rather than a badge that says a page is old.
A restaurant that reprints every season
Send the new PDF to the printer, upload the same file here, read the fifteen things that changed and approve them. The website and the printed menu say the same thing on the same day.
A kitchen that has changed a supplier
The allergens moved on four dishes. Those four come to you individually to read, while the wording tidy-ups elsewhere can be accepted together.
A café putting prices up
Approve every price and leave the descriptions alone. If something looks wrong the morning after, undo it and you are back where you started.
Anyone who has been burned before
Nothing is published by surprise. You see the proposed changes, you decide, and only then does the website change.
Reading a document never touches your live menu — it produces a proposal, and a proposal is something you read. Where the file cannot be read safely, LimeOrigin refuses rather than inventing dishes or prices, and tells you in plain words what happened. What you confirm about your own wording stays with your website and is never pooled with other businesses' menus.
No. It reads menus made on a computer, where the words are really in the file. A photograph or a scan is a picture of a menu, and reading one would mean guessing — so instead you are told plainly that there is no text to read, and your PDF menu carries on working as it is.
Start with a free Origin Session — about 15 minutes — and watch LimeOrigin build around your business.