Current State
Last Updated April 06, 2018, at 05:13 AM
(Includes estimated Acklen percentage complete in light blue)
- Development Environment [100%] [100%]
- New Server
- New Frontend Framework
- New Backend Framework
- IBM DB2 Lib
- Registration [90%] [30%]
- Current Customer Handling
- Dupe Prevention
- Address Management [80%] [10%]
- Assist T File Address Lunacy
- Shipping [70%] [30%]
- Carts [70%] [80%]
- Order Processing [20%] [10%]
- eChecks
- CCs
- Payeezy PCI Bypass
- Payeezy Sandbox
- Product Database [90%] [0%]
- Custom Packages [20%] [0%]
- Returns [0%] [0%]
- Checkout [10%] [10%]
- Payment Plans [30%] [10%]
- Wish List [0%] [0%]
- Rewards [0%] [0%]
- Package Builder [40%] [0%]
- Promos [40%] [10%]
- Taxes [40%] [20%]
- Digital Products [0%] [0%]
- My Account [0%] [0%]
- Export Process [0%] [0%]
- Payment Processing [20%] [10%]
- Admin & Tooling [0%] [0%]
- Site Integration [10%] [0%]
Old Original Acklen Board
Tier 1
- Packages
- Items
- Discounts
- Flex Kits
- Push to Assist
- Payment Plans
- Customer Type
- Promotions
- Inventory From Assist
- Mobile First / Responsive
- Sales Tax
Tier 2
- Shipping
- Coupons
- Migrate Existing Users
- Rewards/Referral Program
- Catalog Requests
- Weight SKUs -> CSS Changes
- Digital Products
- Returns
- Google Analytics
Tier 3
- Clone/Mirror InquisiCart (i.e., BookShark)
- Upsell
- Customer Service Global Access
- Subscription Products
- POS (Tablet)
Tier 4
- Google/FB Checkout
- Hidden Content (Login Required)
- Wishlists
What did Acklen Do?
- Mapping Assist T Files
- They did a good job getting most of what was needed mapped. It has been helpful to speed up our process, but nothing they implemented was 100%. There was always something missing in every piece.
- Built Their Development Environment
- Frontend
- Absurdly over-complicated
- Extremely difficult to work in
- Backend
- Extremely difficult to trace execution flow
- Careless processing
- Deployments
- Incomplete, always needed multiple reconfigurations
- Overly complex, required in-depth knowledge of configs to manage
- Unit Testing
- TDD levels of unit testing
- Takes a lot of time and does little good if it doesn't help keep the application bug-free...
- Packages
- Worked with Robbie to pull from PDB
- Items
- Worked with Robbie to pull from PDB
- Discounts
- Worked with Robbie to pull from Promo System
- Flex Kits
- Push to Assist
- Had initial steps and T File implementations in place, but were mostly incomplete and buggy
- Payment Plans
- Had basic config but no credit check or additional requirements
- Customer Type
- Promotions
- Worked with Robbie to pull from Promo System
- Inventory From Assist
- [Not sure, shouldn't be a top level item anyway...]
- Mobile First / Responsive
- Sales Tax
- Yes (via TaxJar? Which we've now changed to Avalara AvaTax)
- Shipping
- Basic pull from Shippo with little/no regard for our custom requirements
- Coupons
- Worked with Robbie to integrate with Promo System
- Migrate Existing Users
- Rewards/Referral Program
- Catalog Requests
- Weight SKUs -> CSS Changes
- [I don't know what this means...]
- Digital Products
- Returns
- Google Analytics
- Clone/Mirror InquisiCart (i.e., BookShark)
- Upsell
- Customer Service Global Access
- Subscription Products
- POS (Tablet)
- Google/FB Checkout
- Hidden Content (Login Required)
- [Sortof... They provided a terrible auth API that I had to make worse to make usable to accomplish this...]
- Wishlists