Hello. My name is Mousa Batarseh. I build and run online stores for a living. This short film is for the people who run STIIIZY, the cannabis brand from Los Angeles. You do not need any technical background to follow along. I will go slowly, one idea at a time, and I will show you real pages from your own website as we go.

Here is the whole idea in one sentence. Your website is the best place to fall in love with a STIIIZY product, and right now one of the hardest places to buy one.

Let me explain what I mean. STIIIZY has one website people visit, stiiizy dot com, and two separate systems where people buy. Pickup orders run on a menu system called Flowhub. California delivery runs on a second system at shop dot stiiizy dot com. Each store has a live menu with the price, the strength, and the stock for every product.

The website points at those menus with a green button labelled BUY NOW. Think of the button as a hand-off. The website hands the shopper over to a menu on a different web address. The two sides never talk to each other.

On October twenty-fourth, twenty twenty-six, I pressed every BUY NOW button on the cannabis pages of stiiizy dot com. There are seventy-seven of them. Twenty-three led nowhere. A page with no product. On your Batteries page, all five buttons are dead. On the forty's Blunts page, seven out of seven.

Then I looked at prices. The home page shows five featured products with prices. For five of the ten prices, the menu says something different. A gummy pack shows ten dollars on the website and seven dollars at the store menu. A bag of Tropic Jack flower shows twenty-three dollars on the website and eighteen forty at the menu. The same bag on delivery shows twenty-seven dollars on the website, twenty-eight dollars on the menu, and the menu says out of stock.

Then I tried Michigan. STIIIZY runs three stores in Michigan. The Michigan link in your main menu returns an error page. Yet the Ferndale and Kalamazoo menus are live on the same menu system you use in California. The data exists. The website never reads the data.

The usual fix is to retype the prices and relink the buttons. Someone opens the Shopify editor, types in the new price, pastes in the new link, and the page looks right again. For a day. Prices change with deals. Five saved variant links were dead. Retirement with new inventory lots is a plausible cause, which needs vendor confirmation. Retyping does not provide an ongoing check.

And here is the part a normal visit hides. When a visitor lands on a broken brand page, a small piece of code sends the visitor to the product index, store list, delivery page or home page. The visitor sees another page instead of the error. The redirect is observed in the page code. The effect on analytics is inferred. No analytics account was inspected, so the error count is unknown. A real error page, with an event measured in analytics, would make this failure visible.

The solution has one principle: read, do not retype. Both of your menu systems publish the price, the strength, the stock, and the product name inside the code of every product page. Today. The brand website holds hand-typed copies of those facts. Copies rot. So instead of copying, the website reads.

Step one, show a real error page with a store finder, so failures become visible. Step two, point each button at a search for the product, so the link does not depend on a specific variant code. Step three, run a nightly check which reads every card and link on stiiizy dot com, opens each target, and emails a list of what drifted. Step four, read the prices from the menus, with a fallback which says "see price at your store" when the read fails. Step five, keep one table of states and stores, so Michigan, Nevada and New York get real paths.

Now let me walk you through the website I built to show all of this. The address is mousabatarseh dot com, slash stiiizy dash proposal. The page is built around a seam. Everything on the left, on white, is what stiiizy dot com says. Everything on the right, on black, is what the store menu says. Things change when they cross the seam.

At the top, the headline says: pick a product on stiiizy dot com, press Buy, watch what changes. When the page loads, a product card travels from the white side to the black side. Tropic Jack, twenty-three dollars, crosses the seam and becomes eighteen forty, and leaves a grey outline at the starting point. As you scroll, a second card, Pineapple Chunks, crosses and becomes Product Not Found. Beside the stage, two counts: twenty-three of seventy-seven buy buttons led nowhere, and five of ten featured prices changed at the menu. Every number carries the date.

The next section is called Start here. Three short panels explain the website, the menus, and the hand-off, in plain words. This film sits in the same section.

Then a section called Credit where due. Your store menus are native pages, not embedded frames, with tax-included prices and an add-to-bag button. Most cannabis brands have no store of their own to send a shopper to. You have sixty-five in California, a delivery service, and three in Michigan. The pieces exist. The gap sits between them.

Then the five symptoms. The left column stays pinned while you scroll the right column. One, thirty percent of the Buy buttons go nowhere. Two, the first price a shopper sees is often wrong, with a table of the real pairs. Three, Michigan is a four oh four. Four, Google is told every product costs zero dollars, because the product code on one hundred thirty-five pages says price zero, in stock. Five, the brand page hides errors with a redirect. The analytics effect needs access. The actual redirect code is shown. Each card shows the command you run yourself to repeat the test.

Then the mechanism, as a diagram. On the left, the Shopify theme: prices typed into settings, links pasted as text, store lists pasted page by page. On the right, the menus: price, strength, stock and names published on every page, with links built on variant codes. In the middle, a gap, with the words: nothing checks one side against the other.

Then the demonstration. I call the tool Hand-off Check. On the left, you pick a product from twenty-four real cards taken from stiiizy dot com. You pick a channel, pickup at the downtown Los Angeles store or delivery. You pick a state. Then you press Run the check. On the right, the path appears in four steps. Step one, what stiiizy dot com shows: the name, the price, the size label, the strain. Step two, the link: the button text, the destination, and the response code. Step three, what the menu shows: the name, the price, the size, the strain, the strength, the stock. Step four, the verdict: Match, Differs, or Not found, with a chip for each field, a grey chip where the brand site shows nothing, and one plain sentence explaining the gap and the fix.

Let me run three. Tropic Jack, pickup. The brand site said twenty-three. The menu says eighteen forty. The gap is four dollars sixty. The card also says fourteen grams on a three and a half gram bag. Verdict: Differs. Now Pineapple Chunks. The link answers four oh four. Verdict: Not found. Now the Purple Zlushie pod on delivery. Name, price, size and strain agree. Verdict: Match. Three products, three different outcomes, one website.

The second tab lists all seventy-seven links with filters for dead or working and for which web address they point at. The third tab lists all twenty-nine price checks. The fourth tab, Prevent, is a short list of six rules to run before a card goes live, with pass and fail counts from the snapshot. Any view exports to a spreadsheet file, and a button copies the fix list.

The same data lives in a workbook I call the Hand-off Ledger. One sheet per check, with owner and status columns, a blank version to reuse, and the instructions to repeat the test.

Then the fixes, in order, smallest first. Then four tempting fixes and why they lose: retyping every month, embedding the menus as frames, moving the whole site onto the menu system, or copying every menu product into Shopify. Then four numbers to read monthly, so you know the fix worked. Then the method: public pages only, dates and times, what was observed, what was inferred, and what was not tested. I did not test page speed scores, and I did not test Google rankings, so the page says so.

If you want this fixed, the first engagement is two weeks. The question: how many shoppers lose the hand-off, where, and which fixes stop the loss first. I need read access to the Shopify theme, read access to analytics, and one contact at each menu vendor. You get a real error page live, the seventy-seven links repointed, the nightly check running with an emailed report, the ledger filled with owners and status, and a one-page summary. You judge the work by three things: dead links at zero for thirty days, price gaps visible and falling every night, and a Michigan visitor reaching a Michigan menu in two clicks.

The site is at mousabatarseh dot com, slash stiiizy dash proposal. Every figure on the page carries a web address you open in a browser. Nothing in this study touched a live system, and nobody at STIIIZY asked for this work. I live fifteen minutes from your Ferndale store. If you need an ecommerce specialist or website work, write to hire me at mousabatarseh dot com. Thank you for watching.