Hello I need developer specialist for my button bug.
When clients proceed from cart drawer to cart - the place order button its there , disappears , then come back.
Can I know how to fix it , if you need the main-cart-footer.liquid i will send it.
But please help me solve it because the opening is soon and I try my best to look professional.
By design, these 2 apps each control the checkout button, but for different reasons.
Parcely controls it because it wants you to choose a pickup point first. Easify controls it to ensure the product options have been fully loaded before checkout. Both cannot co-exist in their current state, they are just playing tug-o-war.
I would check the app settings, or uninstall one of the apps. You could also try to force it with css. This would go at the bottom of base.css or theme.css
Maximus is spot on with diagnostics.
Making your checkout button always visible/clickable is an option, but it will prevent the apps from working the way they were designed.
Usually, the goal is to shorten the path your visitors have to follow to become customers.
You have a drawer cart, but also a cart page – does this extra step really necessary/worth it?
This looks less like a theme bug and more like a JavaScript app conflict on the cart page.
From the symptoms (button appears → hides → reappears), one script is likely re-rendering main-cart-footer or toggling the checkout CTA after another app modifies the cart DOM.
Since Parcely and Easify were mentioned, I’d test in this order:
Disable one app at a time and retest cart drawer → cart page flow.
Check for duplicate event listeners / MutationObservers firing repeatedly.
Inspect whether the checkout button gets a temporary hidden class (hidden, opacity-0, display:none) then removed.
If confirmed, move the app injection point or exclude the checkout button container from observer scans.
Quick temporary fix before launch: debounce the observer or stop both apps from targeting the same cart footer node.
If no-code launch is urgent, ask whichever app owns the checkout logic to whitelist the cart footer. This is usually faster than editing theme files last minute.
this is happening because of re-render issue by AJAX call,
see if you can edit cart form like this
<form action="/cart" method="post" id="cart">
<button type="submit" name="checkout" class="cart__checkout-button button">
đź”’ Place Order
</button>
</form> de
and you can also use css to fix the layout stick to that position only
Hey,
Thanks for sharing the details I understand how important this is, especially with your launch coming up.
What you’re describing (the “Place Order” button briefly disappearing and reappearing) is usually caused by a JavaScript re-render or cart validation script triggering when the page loads or updates. This often happens with cart drawers, dynamic sections, or apps that modify the checkout/cart behavior.
A few quick things I’d like to check to pinpoint it properly:
– Which theme are you using?
– Have you recently added any cart/upsell/discount apps?
– Does the issue happen consistently or only on first load?
Yes, please go ahead and send over your main-cart-footer.liquid file that will help a lot. I’ll review it and show you exactly what’s causing the flicker and how to fix it cleanly.
We’ll get this sorted so your store looks polished before launch
Agree with the others here, this does sound more like a cart/app conflict than a Shopify checkout issue itself.
The key thing I’d test is whether the checkout button is being re-rendered or temporarily hidden when the cart updates. This can happen when a cart drawer, shipping app, upsell app, discount app, or AJAX cart script modifies the cart state after page load.
A few practical checks I’d run:
Test the full journey on both desktop and mobile
Product page → add to cart → cart page/cart drawer → checkout
Temporarily disable cart-related apps one by one
Especially anything touching shipping, upsells, discounts, cart validation, or the checkout button.
Check the browser console when the button disappears
If there is a JavaScript error during the cart update, that will usually point you in the right direction.
Compare behaviour in a duplicated theme
If the issue disappears in a clean theme or with apps disabled, you can narrow it down much faster.
Be careful with CSS-only fixes
Forcing the button to stay visible can hide the symptom, but if the underlying cart state or checkout payload is broken, customers may still hit problems later in the journey.
The important thing is to test the full path to purchase, not just whether the button appears. A store can look fine visually but still have a broken buying journey after an app or theme change.
For transparency, I build Revenue Shield, a Shopify app that continuously tests these buying journeys across desktop and mobile and alerts you if cart or checkout flows break. Not needed to debug the root cause here, but this is exactly the kind of issue automated journey testing is designed to catch before customers do.