Furlong
A horse racing terminology and reference connector — distances, the Triple Crown, and race-day vocabulary
Discover
OpenAPIUnderstand Stacking3 tools Avoid Surprises4 tools Calculate & Compare2 tools
Stack Rules
How coupon stacking generally works — manufacturer vs. store coupons, exclusions, and a savings calculator
Unify Dynamics LLC
Tools9read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent
Try asking
Real questions, and the tools your agent calls to answer them.
What does coupon stacking even mean?
Tools called
stacking_basicsWhat's the difference between a manufacturer and store coupon?
Tools called
coupon_types_glossaryCan I use a manufacturer coupon and a store coupon together?
Tools called
can_i_stackWhat order do my coupons get applied in?
Tools called
stacking_order_guideWhy didn't my second coupon work?
Tools called
common_exclusionsWhy didn't my digital coupon apply at checkout?
Tools called
digital_coupon_tipsWhat should I check before trying to use two coupons?
Tools called
fine_print_checklistIf I have a 20% off coupon and a $5 off coupon on a $40 item, what's my final price?
Tools called
calculate_stacked_savingsAre grocery stores more coupon-friendly than department stores?
Tools called
retailer_type_patternsAbout
Stackrules is a fully local coupon-stacking rules explainer. stacking_basics explains what stacking means and the core rule (one manufacturer + one store coupon per item is usually fine; two manufacturer coupons on one item essentially never is). coupon_types_glossary defines manufacturer/store/digital coupons, cash-back apps, BOGO, and price match. can_i_stack gives a general yes/no/partial/varies answer for a specific pair of types. stacking_order_guide gives the typical checkout application order. common_exclusions lists patterns that commonly block stacking. digital_coupon_tips covers app/loyalty-loaded specifics. fine_print_checklist is what to check before assuming two coupons will combine. retailer_type_patterns notes how grocery, drugstore, big-box and online-only retailers tend to differ. calculate_stacked_savings is a pure-compute tool: give it a price and an ordered list of percent/dollar discounts and it works out the final price and total savings the way a point-of-sale system typically would. General, retailer-agnostic patterns — a specific coupon's fine print or a specific store's posted policy always overrides anything general here. Keyless; fully local; zero upstream calls; nothing stored.
Sources: Hand-curated from widely observed, generally published US retail coupon practice (not any single retailer's specific policy); the discount-stacking calculator is pure arithmetic on user-supplied values. Fully local, zero upstream calls.
Privacy
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
Data not collectedNo account, no profile, no stored prompts or results.
What it can do
9 tools, grouped by job. Every one is read-only or compute-only.
- Stacking basicsWhat "coupon stacking" means, the core general rule (one manufacturer + one store coupon per item is usually fine; two manufacturer coupons on one…
- Coupon types glossaryDefines manufacturer coupon, store coupon, digital coupon, cash-back/rebate app, BOGO, percent/dollar-off, loyalty discount, and price match.
- Can i stackA general yes/no/partial/varies answer for whether two coupon or discount TYPES typically combine (not whether two SPECIFIC coupons will — always…
- Stacking order guideThe typical order multiple discounts are applied in at checkout: sale price, then loyalty/digital store coupon, then manufacturer coupon, then…
- Common exclusionsPatterns that commonly block stacking regardless of coupon type: explicit "not combinable" language, per-customer limits, size/variety…
- Digital coupon tipsPractical tips specific to app/loyalty-loaded digital coupons: loading before you shop, separate stacking rules from paper coupons, deduplication,…
- Fine print checklistWhat to actually check on a coupon before assuming it'll stack with another: expiration, size/variety, per-customer vs.
- Calculate stacked savingsApplies a list of percent/dollar discounts to a price IN ORDER, the way a point-of-sale system typically processes a multi-coupon transaction, and…
- Retailer type patternsHow coupon-stacking friendliness tends to differ by retailer type — grocery chains, drugstores, big-box/ department stores, and online-only…
Information
PublisherUnify Dynamics LLC
CategoryEveryday life · Shopping
LanguagesEnglish
Built forGlobal
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpoint
https://stackrules.connectorbay.com/mcpREST APIopenapi.json
CountryWorldwide
More like this
Grotto
A caving/speleology reference and safety guide — cave formations, safety fundamentals, and bat conservation
Static
A home audio/video reference and calculator — HDMI specs, speaker wire gauge, resolutions and formats
Splint
Basic first-aid reference — emergency first steps, wound care, CPR and choking overviews, and more
Ensign
A fully local world flags, national symbols, and vexillology reference
Parchment
Genealogy research methodology, record types, citations and DNA basics — a how-to-research guide
Documentation
Back to topWhat Stack Rules is for
"Can I use a manufacturer coupon and a store coupon together?", "why didn't my second coupon work?", "what's my final price with a 20% off coupon and a $5 off coupon?" — a general explanation of how coupon stacking actually works, since it's one of the most commonly misunderstood parts of everyday shopping.
What it does
stacking_basics explains what "stacking" means and the core rule that drives almost all confusion about it:
one manufacturer coupon plus one store coupon per item is usually fine (they're two different companies each
discounting their own side), while two manufacturer coupons on the same single item essentially never is.
coupon_types_glossary defines manufacturer, store, and digital coupons, cash-back/rebate apps, BOGO, percent-
and dollar-off math, loyalty discounts, and price matching. can_i_stack gives a general answer for a specific
pair of types — stackable, not stackable, partial, or "varies too much to say." stacking_order_guide walks
through the typical order discounts apply at checkout, ending with cash-back apps (which are always claimed
after the fact, on your final receipt). common_exclusions lists the patterns that most often block stacking
regardless of type — explicit "not combinable" language, per-customer limits, size/variety mismatches, and the
zero-price floor most registers enforce. digital_coupon_tips covers loading coupons before you shop,
deduplication, and the most common reasons a loaded coupon silently doesn't apply. fine_print_checklist is
what to actually read on a coupon before assuming it'll combine with another. retailer_type_patterns notes how
stacking-friendliness tends to differ between grocery chains, drugstores, big-box/department stores, and
online-only retailers. calculate_stacked_savings is the one real calculator here: give it a price and an
ordered list of percent/dollar discounts, and it works out the final price and total savings the way a
point-of-sale system typically processes a multi-coupon transaction.
What it is not
Everything except the calculator is a general, retailer-agnostic pattern based on widely observed practice — never the actual, specific policy of any store or the terms of any specific coupon. A coupon's own printed fine print, or a retailer's own posted coupon policy, always overrides anything general described here.
Privacy policy
Back to topStack Rules — Privacy Policy
Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Stack Rules is. Stack Rules is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a coupon-stacking rules explainer — general, retailer-agnostic patterns for how manufacturer and store coupons typically combine, plus a stacked-discount calculator. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.
What we receive. The arguments of each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.
Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.
What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.
Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).
Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.
Children. Stack Rules is a general-audience service operated by the adult using the assistant.
Changes. We will post changes here with a new effective date.
Terms of service
Back to topStack Rules — Terms of Service
Effective 25 September 2026. These terms govern use of the Stack Rules connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
- The Service. Stack Rules returns a coupon-stacking rules explainer — general, retailer-agnostic patterns for how manufacturer and store coupons typically combine, plus a stacked-discount calculator. It is accessed through an AI assistant or directly over MCP or HTTP.
- General information, not professional advice. Stack Rules provides general, hand-curated reference information. It does not know your specific product, purchase, brand, or situation, and it is not a substitute for reading the manufacturer's or retailer's own materials, or for professional advice where relevant.
- Reference, not guaranteed-current. Content reflects general, widely published practice as of the build date stated in the Service's own data. Some figures, dates or rules change over time and vary by brand, retailer or region — always verify anything decision-critical against a primary source.
- Acceptable use. Automated use within the published rate limits is welcome.
- Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
- Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
- Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
- Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss, injury, or damage arising from use of, or reliance on, the Service. Our total liability is limited to US $100.
- Governing law. California law; venue in San Mateo County, California.
- Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/stackrules
Support
Back to topStack Rules support
Email agent@connectorbay.com. We answer within two business days.
- MCP endpoint:
https://stackrules.connectorbay.com/mcp - REST API:
https://stackrules.connectorbay.com/openapi.json - Live status: https://stackrules.connectorbay.com/health
When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Stack Rules never asks for them.