Filmtools
Service Request Portal for Sales & Web Teams
Centralizing product requests and improving visibility across departments

Contributions
User Research, Visual Design, User Testing, Prototyping
Stackholders
Blake Buchanan
Customer Service Representative
Charlotte Theret
Web Content Specialist
Timeline
3 weeks
Overview
Filmtools is a leading e-commerce brand serving the film and TV industry. Internally, product addition requests were managed through scattered emails and phone calls, leading to delays and miscommunication. I designed a centralized internal portal that streamlined requests, reduced emails and calls by 90%, and created clear accountability between sales and web teams.
My Role
Customer Service Representative
Problem
Issues
Where the process broke down
Sales and web teams relied on emails and phone calls for product requests, leading to delays, missed items, and frequent miscommunication. The growing request volume overwhelmed this informal system, slowing processing and frustrating both teams.
Business Impact
Consequences for the business
This slowed product updates on the e-commerce site, resulting in missed sales opportunities. Delays and miscommunication increased the risk of publishing errors and undermined team confidence.
| Pain Points | Existing Solutions |
|---|---|
| Teams relied on emails and phone calls, creating delays, confusion, and missed requests | Google Form + Sheet → Easy to set up, but poor for bulk uploads and no accountability. |
| No real-time visibility into request status, causing repeated follow-ups | Magento/NetSuite Modules → Familiar systems, but required customization with limited flexibility. |
| High request volume made prioritization difficult, leading to further delays | Ticketing System → Structured, but not designed for product requests, risk of long-term inefficiency. |

Slide left to right to compare
Objective
User Goals
- Ensure quick adoption by both sales and web teams
- Minimize onboarding with an intuitive, self-service design
- Enable users to confidently navigate and use the portal independently
- Reduce reliance on ongoing support from the web team
Business Goals
- Streamline and centralize the product addition request process
- Replace inefficient email and phone communication
- Reduce delays and improve accountability
- Enhance operational efficiency
- Support faster product updates and increased sales opportunities
Success Metrics
- Monitored daily request volumes via the shared web team inbox
- Gathered ongoing feedback from teams post-launch
- Tracked adoption rate and reduced reliance on email/phone requests
- Identified areas for process improvement through usage monitoring

Research
Research Methods
How we gathered insights
- Conducted casual, in-person conversations with sales and web team members to identify pain points, validate communication issues, and gather early expectations
- Observed workflows daily as part of the web team, tracking how requests were handled via emails and calls to understand habits and bottlenecks
User Insights
- Sales and web teams disliked chasing updates via email/phone, leading to stress, duplicated work, and lost requests
- Users valued clear request status visibility over advanced features
- Short, focused 10-minute feedback sessions were highly effective, proving testing didn’t need to be long or formal
Market Insights
- General ticketing systems (Jira, Trello, Zendesk) → structured but not designed for product requests
- Magento and NetSuite were heavily used internally → so the portal was designed to align with familiar workflows
- In a fast-paced, operational environment, tools needed to be intuitive, require minimal training, and fit into existing habits
Impact
Research directly shaped priorities
User frustration with request status uncertainty drove us to put tracking front and center. The final UI included refreshable, clear status indicators both teams could access instantly.

Design
Ideation
Building on familiar systems
My initial concepts were inspired by the web platforms both teams use daily: Magento and NetSuite. While these tools have their quirks, their familiarity made them a natural foundation for the new portal’s design. I focused on streamlining the most-used elements from these platforms to create an experience that felt intuitive, minimized the learning curve, and aligned with existing workflows.
Design Decisions
Balancing needs and feasibility
I created wireframes based on expected user flows, collaborating with the developer to validate feasibility. After two rounds of stakeholder feedback and revisions, I delivered mockups that surfaced additional needs like bulk uploads and notifications. We resolved through quick sessions, ensuring the design balanced user needs with technical constraints.
User Testing
Validating with real users
We piloted the portal with a test group from the sales department, conducting brief 10-minute sessions that fit their workflow. Since requests should take less than a minute, these quick tests provided actionable feedback for rapid iteration. After refining the tool, we expanded testing to the full team.
Iterations
Refining the experience
During alpha testing with the sales department, we learned that bulk uploads and real-time notifications emerged as essential, and we quickly integrated them despite not being in the original scope. Additional refinements included simplifying form fields, adjusting status indicators for clarity, and optimizing the layout for faster, one-minute request submissions.

Results
User Impact
Value for the user
The portal reduced emails and phone calls by 90%, virtually eliminating lost or delayed requests. Teams could now track status in real time with a page refresh, and every request included submission details for full transparency and accountability.
Business Impact
Value for the business
By aligning the portal with familiar internal tools, onboarding new sales reps became faster and easier. This minimized ramp-up time, improved operational efficiency, and enabled faster product updates with fewer bottlenecks.
Lesson Learned
What we’d do differently
While we had a clear project plan, the absence of a dedicated project management tool or manager introduced challenges.
We relied on a color-coded Google Doc to track tasks and milestones, which worked to a degree but lacked structure.
In hindsight, a project manager or a formal tool like Trello or Asana would have improved time management, milestone tracking, and alignment, reducing risks tied to time constraints.
Looking towards the future
Next steps
Future iterations will include a landing dashboard to give users an at-a-glance view of request progress, further streamlining transparency and efficiency.

Filmtools
Vendor Integration for Automated Inventory Sync
Replacing bulk uploads with a live API connector for Filmtools' inventory management

Contributions
User Research, Visual Design, User Testing, Prototyping
Stackholders
Nick Lampke
Operations Manager
Anna Rodriguez
Purchasing Agent
Timeline
2 weeks
Overview
Following the successful launch of the service request portal, other departments began exploring how the tool could improve their workflows. The purchasing team, in particular, had been using a bulk upload tool to manually update inventory levels for hundreds of SKUs daily. I designed a tool that integrated one of our primary vendors, enabling automated hourly inventory syncing and eliminating the need for manual uploads for that vendor.
My Role
Operations Manager
Problem
Issues
What got in the way
Purchasing relied on bulk spreadsheet uploads to manage vendor inventory updates in NetSuite. Without a direct integration, counts updated only once daily in the morning.
This delay led to inaccurate stock levels, operational inefficiencies, and downstream impact on customer orders.
Business Impact
Why it mattered
This inefficient workflow delayed product updates on the e-commerce site, resulting in missed sales opportunities, increased risk of errors, and extra hours spent reconciling orders.
| Pain Points | Existing Solutions |
|---|---|
| Inventory levels were often inaccurate due to delayed updates | Excel Sheets → functional when processed manually but highly prone to human error |
| Bulk uploads were error-prone, requiring manual item-by-item verification | NetSuite Native Module → reliable for managing inventory but lacked a connector for this specific vendor |
| DCKAP EDI Connector → a 3rd party solution, but prohibitively expensive for this use case |
Objective
User Goals
- Eliminate the need for purchasing to manually double-check inventory levels
- Remove reliance on uploading large, error-prone spreadsheets
- Free purchasing to focus on managing smaller vendors
- Use the portal primarily for syncing and edits rather than manual data entry
Business Goals
- Provide customers with accurate, real-time inventory availability
- Reduce risk of out-of-stock scenarios at checkout
- Improve overall customer satisfaction by streamlining order processing
Success Metrics
- Track frequency of vendor connector interactions
- Monitor reduction in manual spreadsheet uploads for this vendor
Research
Research Methods
Approach to discovery
- Conducted in-person interviews with the purchasing team to map workflows and pain points
- Observed typical user workflows to uncover inefficiencies and manual workarounds
User Insights
- Observed purchasing staff frequently correcting inventory discrepancies and contacting vendors for updates
- Users cross-checked item availability between ERP and website, which introduced errors and slowed processing
Impact
How findings guided design
Confirmed the need for real-time inventory syncing with vendor systems, eliminating manual uploads and reducing errors. This priority became the foundation for the vendor connector initiative.
Design
Ideation
Starting from what existed
I began by referencing the existing item request table layout, making targeted adjustments to better align with the purchasing team’s workflow.

Design Decisions
Balancing familiarity and clarity
To minimize training time and friction, I retained the familiar table structure and interface conventions. The team prioritized seeing accurate list counts and and immediate access to pull and sync controls, which we surfaced prominently in the updated design.
User Testing
Validating with real users
We began with 10–15 minute phone interviews with two purchasing staff members, followed by in-person sessions for deeper insights. Feedback confirmed the importance of real-time list counts and the convenience of direct sync access, validating our design approach.
Iterations
Refining the experience
Based on testing feedback, so we added individual item syncs, giving staff more granular control without over-syncing.

Slide left to right to compare
Results
User Impact
Did it make life easier?
The tool eliminated the need for manual bulk uploads for the vendor, reducing daily inventory update errors and freeing purchasing staff 2–3 hours weekly to focus on higher-value vendor management.
Business Impact
Did it move the needle?
Customers could now confidently engage with products previously labeled as out of stock, leading to improved checkout rates (12%) and reduced cancellations (-8%).
Lesson Learned
What we discovered
We realized earlier identification of the vendor’s API availability would have shortened the timeline. The delay in obtaining access slowed testing and integration.
Looking towards the future
What’s next?
Future iterations will extend this integration to more vendors, with a streamlined dropdown selector for multi-partner syncing.

Ready to go back to the main page?
Go back
