iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A sustainable indie workflow is a repeatable loop: define a small player promise, prototype its riskiest assumption, ship a playable build every two to four weeks, learn from playtests, and cut work before capacity is exceeded. Treat sustainable pace as a production constraint, not a wellness slogan.
What a sustainable workflow looks like
Sustainability means the team can deliver useful, playable increments at a predictable pace without relying on routine overtime. Problems remain visible, recoverable and small enough to fix. The workflow protects the core game from uncontrolled additions while leaving time for testing, accessibility, platform compliance and support.
There is no dependable industry-wide percentage for burnout or crunch among small indie teams, so a team should measure its own signals instead: missed commitments, rising defect age, repeated rework, skipped playtests, declining review quality and people regularly working beyond their agreed hours.
Several current figures support a small-scope approach, but they are not universal benchmarks:
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
| Finding | Qualification |
|---|---|
| 52% of developers prioritize smaller-scale projects to reduce risk | Unity 2026 developer survey/report figure |
| 67% of polled developers spend three months or less prototyping | Unity 2026 survey figure; the sample and method determine how far it generalizes |
| 64% of studios with fewer than 10 team members use Unity | Unity 2026 report figure, not a measure of engine quality or project success |
| Median project-development time fell from 91 hours to 21 hours | Unity’s proprietary project-development measure, comparing January 2022 with December 2025; it is not an industry-wide productivity benchmark |
At a Global Game Jam participant survey with 198 responses, frequently used practices included continuous integration, a minimum viable product, scope management, version control, stand-ups, internal playtesting, regular communication and proactive planning. These practices are useful because they shorten feedback loops; they do not guarantee a sustainable result by themselves.
“How you and your team spend time is key to achieving a sustainable development workflow.”
— Isadora Rodopoulos, Coldblood Inc., GDC session
1. Frame a game small enough to finish
Write the player promise
Describe the experience in one sentence that names the player, action and payoff. For example: “A solo player steers a damaged research vessel through short, replayable storms, choosing which systems to repair before the next wave.” The sentence is a decision filter. A proposed feature must strengthen that promise or it is a candidate for later, not a current commitment.
Set the audience and platform before production
Record the primary audience, input method, target devices, display constraints and distribution channel. A keyboard-and-mouse PC game, a controller-first console game and a touch game have different interaction, performance and certification risks. Choose one primary platform for the first release; list other platforms as explicit follow-on options.
Define the core loop
Write the smallest repeatable sequence: input, immediate response, meaningful decision, consequence and reset or progression. A loop such as “explore, choose a route, survive an encounter, spend a reward, repeat” is concrete enough to prototype. Systems outside that sequence are not automatically part of the minimum game.
Create a minimum viable game and cut lines
Make a one-page scope contract containing:
- One player promise and one core loop.
- The minimum number of levels, encounters or scenarios required to demonstrate the loop.
- Required controls, save behavior, accessibility options and platform features.
- Features explicitly excluded from the first release, such as multiplayer, procedural generation, extra modes or additional platforms.
- Quality thresholds for frame rate, crash rate, input response, readability and completion.
Put the cut lines where everyone can see them. When a new idea arrives, classify it as “now,” “later” or “never,” and record who made the decision and why. A feature cannot enter “now” without an owner, an estimate, a testable acceptance condition and an item removed or deferred to make room.
2. Prototype the riskiest assumption first
Rank risk by consequence, not excitement
List assumptions under four headings: feel, readability, technical feasibility and production cost. Rank each by the damage caused if it proves false. A novel movement mechanic that determines the entire game is a higher-risk prototype than a cosmetic menu. Test the highest-consequence assumption before building content around it.
Use disposable, low-fidelity work
Prototype with placeholder art, temporary audio and the shortest path to a playable interaction. The objective is evidence, not polish. Keep the prototype separate from production code when that makes deletion safer. Do not expand the prototype into a full architecture until the core loop earns that investment.
Define a pass or fail signal
Before testing, write what would change your decision. Examples include:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
- New players understand the objective without spoken explanation.
- Players can perform the primary action consistently after a short tutorial.
- The response to an input is readable at the target frame rate and display size.
- A representative scenario can be built within the available content budget.
- The team can implement, debug and test the mechanic with its current skills and tools.
Run a short internal session, record observations separately from proposed solutions, and decide whether to keep, alter, replace or drop the assumption. A failed prototype is useful when it prevents months of production work.
3. Plan two-to-four-week playable iterations
Choose one objective per cycle
Each iteration should end with a playable build that demonstrates one outcome, such as “a new player can complete the first encounter and understand the upgrade choice.” Avoid a list of unrelated department goals. A single objective makes trade-offs visible when time or capacity changes.
Break work into reviewable tasks
Make tasks small enough to finish and inspect within the cycle. “Implement enemy system” hides risk; “spawn one enemy, expose its attack telegraph and add a repeatable test scene” is reviewable. Every task needs an owner, a definition of done, dependencies and a verification method. Keep a visible risk and decision log beside the task board.
Use a repeatable cycle
- Start: confirm the objective, acceptance conditions, available capacity and risks. Remove work that does not serve the objective.
- Build: integrate changes into the shared repository continuously. Keep unfinished work behind a branch, feature flag or isolated scene when it would make the main build unstable.
- Check: run automated checks and a short playable smoke test whenever a meaningful change lands.
- Review: show the build to the whole team and play it with people who did not implement the feature.
- Close: record evidence, defects, decisions and questions; then hold a short retrospective before planning the next cycle.
A two-week cycle provides fast feedback when the team is small or the mechanic is uncertain. A four-week cycle gives more room for content or platform work but needs an interim checkpoint so integration problems do not wait until the end.
Example cycle plan
| Time | Focus | Evidence required |
|---|---|---|
| Day 1 | Objective, acceptance conditions, risk review and task slicing | One-page cycle brief and updated decision log |
| Days 2–6 | Core implementation and daily integration | Runnable build and automated checks |
| Days 7–8 | Content pass, accessibility pass and bug fixing | Playtest candidate with known-issue list |
| Day 9 | Internal playtest and playable review | Observed behavior, defects and player questions |
| Day 10 | Retrospective and re-scope | One or two process changes and the next objective |
4. Prevent scope creep with explicit change control
Separate ideas from commitments
Keep an idea backlog that cannot silently become planned work. During cycle planning, select only the items that fit the objective and capacity. Label each item as a hypothesis, a requirement, a defect or a quality improvement; each category has a different decision standard.
Apply a substitution rule
If a proposed feature enters the current release, remove or defer work of comparable effort and risk. Show the trade-off in the plan. This turns “just one more feature” into a visible schedule decision rather than unpaid overtime.
Use a scope-threat test
Cut or defer a feature when it threatens any of these:
- The clarity or reliability of the core loop.
- The next playable review date.
- Required accessibility, platform or save-data work.
- The team’s agreed capacity and recovery time.
- The ability to produce a clean, testable build.
Prefer depth in the smallest complete experience over breadth that leaves every system half-finished. A cut list is a sign of control, not failure.
5. Make the repository and toolchain boring
Document a predictable project structure
Choose naming, folder, scene, prefab or resource conventions before the project grows. Keep source assets, editable project data, tests, build scripts and documentation in obvious locations. Generated imports, caches and local settings should remain out of version control where the engine permits; document the ignore rules so a new contributor can reproduce them.
Make a clean checkout buildable
Have another team member clone the repository, install the documented engine version and produce a playable build without private files or undocumented steps. Record required SDKs, environment variables, credentials handling, build targets and expected output paths. Repeat this check after major engine or plugin changes.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Review binary assets deliberately
Large textures, audio files, models and source art can make history expensive and merges difficult. Set size limits, use a storage approach suited to large binaries, and require an explicit review for files above the limit. Never overwrite a shared binary casually; coordinate changes and keep the source asset identifiable.
Automate recurring work when it repays maintenance
Start with the failures that interrupt everyone: project import, compilation, unit or integration tests, a launch smoke test and a representative build. Automate a task when it recurs often enough that maintenance costs less than repeated manual work. Keep the pipeline’s failure message actionable and run it on the same operating systems or containers used for release where practical.
6. Choose an engine and production stack by risk
Do not choose an engine because a framework name promises sustainability. Evaluate the complete stack against the team’s project and constraints:
| Decision axis | Questions to answer | Evidence to collect |
|---|---|---|
| First playable speed | How quickly can the team test the core loop? | Time-boxed prototype using the intended input and target device |
| Familiarity and onboarding | Can every contributor debug and review the project? | Pairing session and a clean-checkout exercise |
| Source control, builds and tests | Can changes integrate and produce a known build reliably? | Repository trial, automated smoke test and build log |
| Asset import and iteration | How long does a change take to appear in-game? | Measured import, iteration and recovery steps on representative assets |
| Target platforms | Are input, performance, packaging and certification supported? | Early device build and platform requirement checklist |
| Licensing and services | What recurring fees, hosted dependencies or policy changes affect the plan? | Current terms reviewed before commitment and a fallback plan for critical services |
| Long-term maintenance | Can the team update the engine without destabilizing the game? | Upgrade test branch, dependency inventory and rollback procedure |
Unity and Godot workflow considerations
Both can support a small-team workflow when the team standardizes project structure, version control, builds and testing. Unity’s 2026 report says 64% of surveyed studios with fewer than 10 people use Unity; that describes adoption in that survey, not a recommendation or a guarantee of lower risk. Godot’s official documentation emphasizes intentional project organization and version-control practice. For either engine, test the actual project rather than extrapolating from engine popularity.
Compare the two candidates with the same prototype, repository exercise and target-device build. Record iteration time, onboarding questions, import friction, test coverage, licensing obligations and the cost of changing direction. The best choice is the one that keeps the team’s highest risks observable and recoverable.
7. Integrate continuously and keep feedback short
Use one shared source of truth
Agree on the protected branch or equivalent, review expectations, branch lifetime and merge ownership. Integrate small changes frequently rather than allowing long-lived branches to diverge. A change is not complete when it works on one computer; it is complete when it is integrated, tested and documented well enough for another contributor to use.
Define a smoke test
A smoke test should launch the game, reach the first interactive state, exercise the primary input, load a representative scene and exit or save cleanly. Keep it fast enough to run on every build. Add targeted tests for calculations, progression, serialization and other rules where a regression would be expensive to discover through manual play.
Track build health visibly
Display the latest successful build, commit identifier, target platform, test result and known blockers. When a build breaks, stop adding unrelated work until the failure has an owner and a recovery plan. This prevents a growing pile of unverified changes from hiding the source of a defect.
8. Playtest and review the actual game
End every cycle with a playable review
Review the build in the same mode players will use: correct input device, display settings and target performance budget. Invite at least one person who did not implement the feature. Ask them to play before explaining the intended behavior. Capture what they did, where they hesitated, what they misunderstood and what they enjoyed.
Keep evidence separate from ideas
Use four records:
- Observations: what the player or build actually did.
- Defects: behavior that violates an agreed requirement or quality threshold.
- Questions: uncertainties requiring a decision or further test.
- Ideas: optional improvements that do not yet have a commitment.
This separation prevents a speculative solution from being mistaken for a confirmed problem. Prioritize fixes by player impact, reproducibility and risk to the core loop.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Include accessibility early
Check text size and contrast, remappable controls where feasible, subtitle and audio options, readable feedback without relying on color alone, pause behavior and motion or flashing risks. Testing these during each iteration is cheaper than redesigning the interaction after content and tutorials depend on it.
9. Retrospect, then re-scope
Ask questions that change the next cycle
A useful retrospective is short and specific:
- What created player value this cycle?
- What caused rework, waiting or integration failure?
- Which assumption remains untested?
- What single process change will we try next?
- What should be removed, reduced or reordered?
Assign an owner and a check date to each process change. If the same problem returns, change the system around it: reduce work-in-progress, split tasks more finely, move a test earlier or revise the acceptance condition.
Re-estimate from evidence
After each playable review, update the remaining scope using observed throughput and defect load, not the original optimism. If the release date is fixed, cut scope. If the scope is fixed, move the date or add capacity deliberately. Do not solve an arithmetic mismatch with unplanned overtime.
10. Protect team health as a production requirement
Make workload visible
Limit simultaneous priorities and show unstarted, active, blocked and review-ready work. Rotate operational chores such as build maintenance, release packaging, bug triage and meeting facilitation so one person does not become a permanent bottleneck.
Create a no-penalty escalation path
Anyone should be able to flag overload, a quality risk, an unsafe schedule or a blocked dependency without being punished for slowing the plan. Define who receives the signal, how quickly the team responds and what information is needed. Treat an early warning as production data.
Use a hard decision rule for overtime
If a milestone requires routine overtime, change scope, sequencing, staffing or the date before adding more hours. Short exceptional effort may occur during a release incident, but it needs a recovery plan and must not become the hidden baseline. A sustainable workflow is demonstrated by predictable delivery and recoverable problems, not permanently high personal hours.
11. Reserve a real stabilization and release phase
Do not treat polish as an unplanned final week. Create explicit work for performance profiling, memory and load checks, accessibility verification, platform requirements, localization, store assets, crash reporting, save-data migration and support documentation.
Use a release checklist
- Target-device performance and memory budgets pass.
- New, returning and migrated save files behave correctly.
- Required ratings, disclosures, privacy text and platform metadata are complete.
- Store screenshots, descriptions, icons and localization are approved.
- Input, accessibility and language settings survive restart.
- Known issues have severity, player impact and a support response.
- A rollback or hotfix build can be produced from a tagged commit.
Freeze only the parts that must be stable. Continue fixing high-impact defects while avoiding speculative features that could destabilize the candidate build.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.12. Plan sustainable post-launch support
Set a support budget before release: people, hours per week, response targets and the date when active development will be reviewed. Triage defects by player impact, frequency, data loss risk and workaround availability. Schedule post-launch features only when they do not destabilize the core product or consume the team’s recovery capacity.
Maintain a known-issues page, reproducible bug reports and a release log. When a hotfix is needed, branch from the released tag, make the smallest verified change, test the affected save and platform paths, and merge the fix back into ongoing development.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
13. Lightweight kanban or time-boxed iterations?
Neither method prevents crunch. Choose the flow that exposes your team’s dominant risks and still produces regular playable evidence.
| Axis | Lightweight kanban flow | Two-to-four-week time-boxed iterations |
|---|---|---|
| Iteration length | Continuous; work moves when capacity opens | Fixed cycle with a defined playable objective |
| Documentation overhead | Low initially; requires strong item definitions and decision records | Moderate; cycle brief, acceptance conditions and retrospective are explicit |
| Feedback latency | Very short for small tasks, but a playable milestone can drift without a scheduled review | Predictable review at the end of each cycle, with mid-cycle checks needed for four-week cycles |
| Automation investment | Useful for keeping a continuously releasable main line healthy | Useful for repeatable checks before the planned review build |
| Distributed work | Works when status, ownership and decisions are written down | Works when the objective and review evidence are shared asynchronously as well as live |
| Cost of changing direction | Low for unstarted work; high if priorities change while many items are active | Low at cycle boundaries; disruptive when the team interrupts a cycle repeatedly |
| Best fit | Support, bug fixing and small independent improvements | Uncertain mechanics, content slices and work that benefits from a playable checkpoint |
A hybrid is often practical: kanban for defects and operational work, with a time-boxed objective for the next playable slice. Keep work-in-progress limits and do not let urgent support silently consume the entire planned capacity.
14. Measure the workflow without creating bureaucracy
Review a small dashboard at each retrospective:
- Percentage of planned cycle objectives demonstrated in a playable build.
- Time from a change being ready to its first integrated build.
- Age of the oldest high-impact defect.
- Number of reworked tasks and the reason for rework.
- Playtest observations that changed a decision.
- Build failures and average recovery time.
- After-hours work and whether it was followed by recovery time.
Use trends, not individual scores. A falling integration time is helpful only if build quality and team capacity remain healthy. Do not reward a team for closing tasks while the playable experience, accessibility or defect backlog deteriorates.
15. Common failure modes and recovery steps
The prototype became the game
Symptom: placeholder code is difficult to change and every experiment requires cleanup. Recovery: freeze expansion, extract the smallest validated interaction, and rebuild only the production slice needed for the next playable objective.
Every task is urgent
Symptom: the board is full, priorities change daily and nothing reaches review. Recovery: set a work-in-progress limit, name one cycle objective and move unselected ideas to the backlog with a decision date.
The main branch is unreliable
Symptom: contributors keep local fixes and avoid integrating. Recovery: restore a minimal smoke test, assign one owner to the broken build, revert the smallest risky change and require a clean checkout before resuming normal merges.
Playtesting happens only at the end
Symptom: the team debates opinions about fun, clarity or difficulty after months of content work. Recovery: make a rough playable review a cycle acceptance condition and test the riskiest player assumption before adding dependent content.
Release work crowds out development
Symptom: localization, platform checks, store assets or save migration appear in the final days. Recovery: create release tasks early, test one target-device build during each major milestone and reserve explicit stabilization capacity.
Overtime is treated as the plan
Symptom: delivery depends on repeated late nights and recovery work is invisible. Recovery: show actual capacity, cut or reorder scope, move the date or add staffed capacity, then document the decision. Do not normalize the exception.
A practical first month
- Week 1: write the player promise, target platform, core loop, minimum viable game and cut lines. Set repository conventions and create a clean-checkout build.
- Week 2: prototype the highest-risk assumption with placeholders. Define pass or fail signals and run an internal playtest.
- Week 3: plan the first two-week playable cycle, slice tasks, add a smoke test and integrate changes daily.
- Week 4: review the playable build, separate observations from defects and ideas, hold a retrospective, and remove work that threatens capacity or the core loop.
Repeat the loop. Each cycle should leave the game more understandable to a new player, more reliable to build and more honest about what the team can finish.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
