Customer Pickup & Counter Collection Log

1. How to use this log

Use this log each time an order, parcel, repair item or reserved product is handed over to a customer at a service counter, collection point or collection window. Complete the sections in order where possible, and record any exceptions at the moment they are noticed. Fields marked as required must be completed before the record is closed.

This template is provided as a general-purpose record-keeping aid. It is not legal, regulatory or professional advice. Adapt the wording, retention rules and identity-check steps to your own operating procedures and local expectations.


Log entry date and time

Log or reference number

Staff member completing this log

Type of collection


2. Collection point and location details

Store, branch or collection point name

Counter, window or desk identifier

Site or facility address

Collection zone or storage area the item came from

How was the item retrieved for handover?



Was a designated collection window or appointment slot used?


3. Order and transaction reference details

Order, ticket or transaction number

Customer account or membership number

Order or booking date

Date the item became ready for collection


Sales channel or point of order

Salesperson or account contact

Current status of the order before handover



Is this collection linked to a previous order, return or exchange?


4. Customer and collector identity

Record the details of the person actually collecting the items. Only request identity information that your own procedures require, and handle any captured data with appropriate care.


Customer full name

Collector full name (person at the counter)

Is the collector the same person as the customer?


Customer phone number

Customer email address

Collector phone number (if different)

Collector email address (if different)

Collector postal or billing address

Organization or company name (if applicable)

Preferred language for communication

5. Identity and authorization checks

Follow your own organization's procedures when verifying who is collecting an item. The questions below are for record-keeping only and do not define any legal requirement.


What was used to confirm the collector's identity?



Was a pre-arranged proxy or authorized representative used?


Was any additional approval required before release?


The collector's details above were checked against the order record and matched.

Any identity information recorded here will be stored and handled in line with our internal data-handling procedure.

6. Items released for collection

List every item handed over during this visit. Quantities and prices are entered for record-keeping; the line total column calculates automatically from the collected quantity and unit price.


Item release list

Item description

SKU/product reference

Qty ordered

Qty collected

Unit price

Line total

Verified at handover

Cordless drill kit with case
TL-18V-220
1
1
$189.00
$189.00
Replacement battery pack
BAT-18V-40
2
2
$79.50
$159.00
Protective carry bag
BAG-PRO-11
1
0
$24.00
$0.00
 
 
 
 
 
$0.00
 
 
 
 
 
$0.00
 
 
 
 
 
$0.00
 
 
 
 
 
$0.00
 
 
 
 
 
$0.00
 
 
 
 
 
$0.00
 
 
 
 
 
$0.00

Total number of individual pieces handed over (including packaging units)

Total weight of the collection (optional)

Units used for the weight entry above

Were any items partially fulfilled or substituted?


Are any items still to be collected at a later date?


7. Packaging, handling and special requirements

What packaging or protective materials were supplied with the items?


Seal, tag or security reference numbers

Did the customer request any special handling or assistance?



Were any handling, safety or care instructions explained to the customer?


The customer confirmed the packaging was intact and acceptable at the point of handover.

8. Payment, balance and receipting

Total order value

Amount already paid before this collection


Balance collected at the counter

Balance still outstanding after this collection


Which payment methods were used at the counter?



Payment or receipt reference number

How was the receipt or proof of collection provided?


Was any discount, price adjustment or goodwill gesture applied at the counter?


Is a refund, credit note or price difference still to be processed?


9. Condition check and verification at handover

Complete these checks together with the customer where practical, so that any disagreement is identified before the items leave the counter.


Please rate each aspect of the items at the point of handover

Very poor

Poor

Acceptable

Good

Excellent

Not applicable

Outer packaging condition

Product appearance and finish

Completeness of accessories and parts

Cleanliness and presentation

Labels, seals and security tags

Visible signs of damage or wear

Overall condition of the consignment at handover



Was a functional or power-on test performed before release?


Were photographs or a video record taken at the point of handover?


Upload a photo of the items or packaging at handover (optional)

Choose a file or drop it here

Upload any supporting document such as a packing list, inspection sheet or delivery note (optional)

Choose a file or drop it here
 

10. Discrepancies, exceptions and issue handling

Was any discrepancy, delay or problem recorded during this collection?


Please describe what happened, when it was noticed and who was involved:

How was the issue resolved or escalated?



Issue, case or incident reference number

Target date for resolving any open item

Does the customer need to return to the counter to complete this collection?


The customer was informed of the issue, the next steps and the expected timeframe before leaving the counter.

11. Communication and notification preferences

How should the customer be contacted about this collection?


Would the customer like to be notified when future orders are ready for collection?


Preferred contact time window

Does the customer require any accessibility or communication adjustments for future visits?


The customer agreed to receive an electronic copy of this collection record.

12. Collection experience feedback

How would you rate the overall collection experience?

Please rate the following aspects of the counter service

Very dissatisfied

Dissatisfied

Neutral

Satisfied

Very satisfied

Not applicable

Waiting time before being served

Clarity of the information provided

Friendliness and courtesy of staff

Accuracy of the order handed over

Cleanliness and layout of the collection area

Ease of completing payment

Confidence in the identity and handover checks

How did the customer feel about this visit overall?

How likely is it that the customer would use this collection service again?

Please rank these improvements in order of importance to the customer (1 = most important)

Shorter waiting times

Longer or extended collection hours

Faster readiness notifications

More collection points or lockers

Clearer collection instructions

Better packaging and protection

More self-service collection options

What did the customer appreciate most about this visit?

What could be improved for next time?

Would the customer like someone to follow up on their feedback?


13. Internal review and record keeping

Reviewed or audited by (supervisor or quality check)

Review date

Outcome of the internal review


How long should this record be retained?

Storage location or system for this record

Any personal details collected here are limited to what is needed for this collection and will be handled in line with internal data-handling practice.

All mandatory fields in this log have been completed before closing the record.

14. Confirmation and signatures

By signing below, the collector confirms that the listed items were received at this counter, that the condition and quantity were checked as recorded, and that any issues noted in this log were explained to them. Signing does not replace any separate agreement, warranty document or receipt that may apply.


I confirm that I have received the items listed in this log and that the details recorded are accurate to the best of my knowledge.

I understand that any outstanding items, payments or issues recorded here will be followed up separately.

Collector signature

Collector full name (printed)

Date and time of collector signature

Staff member signature

Staff member full name (printed)

Date and time of staff signature

Supervisor signature (if required by your procedure)

Final notes or handover remarks

Analysis for Customer Pickup and Counter Collection Log Form

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.



Overall Form Analysis

The Customer Pickup & Counter Collection Log Form is a thorough, well-structured operational record designed to document every stage of a counter-based handover — from initial log entry through identity verification, item release, payment handling, condition checks, exception management and final sign-off. The form covers twelve distinct sections, each building on the previous one to create a complete audit trail of the collection event. Its breadth and logical sequencing make it suitable for a wide range of retail, service and fulfilment environments where items are physically handed to customers at a counter or collection point.


How to Use This Log

This opening section establishes clear usage guidance and captures the foundational metadata for each log entry. The introductory paragraphs set expectations about completing sections in order and recording exceptions as they arise — a practical instruction that supports data quality and timeliness.


Log entry date and time anchors the record to a specific moment, which is essential for chronological record-keeping and for any later review or investigation. Log or reference number provides a unique identifier that allows this record to be cross-referenced with other operational systems. Staff member completing this log establishes accountability and identifies who was responsible for the entry. Type of collection uses a single-choice format with eight options and a follow-up free-text field for the 'Other' category — a design that balances structured categorisation with flexibility for unusual scenarios.


Collection Point and Location Details

This section captures where the collection took place and how the item reached the counter. Store, branch or collection point name is mandatory and identifies the physical site, which is operationally important for multi-site organisations. Counter, window or desk identifier and Site or facility address add granularity for larger facilities. Collection zone or storage area the item came from traces the internal movement of the item.


How was the item retrieved for handover? is a well-designed single-choice question with conditional follow-ups that adapt to the selected option — for example, requesting an originating branch when items were transferred between locations, or an expected arrival date when items are still in transit. This conditional logic keeps the form relevant and avoids unnecessary questions. Was a designated collection window or appointment slot used? uses a yes/no branching structure that captures either the appointment reference or the alternative arrangement method, demonstrating thoughtful design for varied collection workflows.


Order and Transaction Reference Details

This section links the physical handover to the underlying commercial transaction. Order, ticket or transaction number is mandatory and serves as the primary cross-reference key. Date the item became ready for collection and Sales channel or point of order are also mandatory, supporting fulfilment tracking and channel analysis. Current status of the order before handover is particularly well-designed — its six options cover common pre-handover states, and conditional follow-ups capture details about outstanding payments, missing documents or back-ordered items only when relevant. The question Is this collection linked to a previous order, return or exchange? adds traceability for complex transaction chains.


Customer and Collector Identity

This section distinguishes between the customer (the account holder or order owner) and the collector (the person physically present at the counter). This distinction is operationally important because third-party collections may require different verification steps. The introductory paragraph appropriately reminds users to handle identity data with care and to only collect what their procedures require.


Customer full name and Collector full name (person at the counter) are both mandatory, ensuring both parties are documented. Is the collector the same person as the customer? is a mandatory yes/no question with a follow-up explanation field when the answer is 'No' — this captures the reason for third-party collection efficiently. Customer phone number is mandatory and provides a primary contact channel. The optional fields for email addresses, postal address, organisation name and preferred language add useful context without overburdening the core workflow.


Identity and Authorization Checks

This section documents how the collector's identity was verified. The introductory paragraph appropriately frames these questions as record-keeping tools rather than legal requirements. What was used to confirm the collector's identity? is mandatory and offers six verification methods with targeted follow-ups — for example, requesting document reference numbers for photo identification or an explanation when no formal check was performed. The questions about pre-arranged proxies and additional approvals capture important authorization chain details. The two checkboxes at the end — confirming that collector details were matched against the order record and that identity data will be handled appropriately — reinforce accountability and data-handling awareness.


Items Released for Collection

This section provides a structured item-level record. The Item release list table includes columns for description, SKU, quantities ordered and collected, unit price, an automatically calculated line total (using the formula column4*column5) and a verification checkbox. The pre-populated example rows demonstrate how partial fulfilments appear — one item shows zero collected quantity and zero line total, clearly indicating it was not handed over. Total number of individual pieces handed over is mandatory and provides a quick summary figure. Optional weight and unit fields add flexibility for logistics-relevant contexts. The questions about partial fulfilments and items still to be collected capture follow-up obligations efficiently.


Packaging, Handling and Special Requirements

This section documents the physical presentation of the items and any customer assistance needs. What packaging or protective materials were supplied with the items? is a multiple-choice question with eight options and a follow-up for 'Other', capturing packaging details comprehensively. Did the customer request any special handling or assistance? covers accessibility needs, loading help and other practical requests with relevant follow-ups. The question about handling or safety instructions being explained — with yes/no branching that either lists which instructions were covered or asks why none were — supports service quality documentation. The checkbox confirming packaging was intact and acceptable at handover provides a clear customer acknowledgement point.


Payment, Balance and Receipting

This section handles the financial dimension of the collection. Total order value and Balance collected at the counter are both mandatory, ensuring the key financial figures are always recorded. Which payment methods were used at the counter? is a multiple-choice question with conditional follow-ups for specific methods — for example, cash amount received, bank transfer reference or gift card digits. This design captures payment detail efficiently without requiring all fields for every transaction. How was the receipt or proof of collection provided? documents the customer's receipt preference and delivery method. Questions about discounts, goodwill adjustments and pending refunds capture financial exceptions and follow-up obligations.


Condition Check and Verification at Handover

This section is designed for joint inspection with the customer before items leave the counter. The matrix rating question covering six aspects of item condition — from packaging to visible damage — uses a six-point scale including 'Not applicable', which is a thoughtful inclusion for items where certain checks do not apply. Overall condition of the consignment at handover is mandatory and its five options with conditional follow-ups capture specific issues (cosmetic problems, damage, incompleteness) with descriptive detail. The optional functional test question, photograph/video documentation fields and file upload options support thorough verification practices.


Discrepancies, Exceptions and Issue Handling

This section provides a structured approach to recording and resolving problems. Was any discrepancy, delay or problem recorded during this collection? is mandatory and gates the subsequent detail questions. When issues occur, the multiple-choice question captures the issue type, and the free-text description field with its helpful placeholder example prompts staff to record what happened, when and who was involved. How was the issue resolved or escalated? offers eight resolution pathways with targeted follow-ups. The incident reference number, target resolution date and return-visit question support ongoing case management. The checkbox confirming the customer was informed before leaving the counter is a strong accountability measure.


Communication and Notification Preferences

This section captures how the customer wishes to be contacted and any service adjustments needed. The multiple-choice contact method question covers seven channels with a follow-up for messaging app identifiers. The future notification preference question with its notice-period options supports proactive service. The accessibility adjustments question demonstrates inclusive service design. The checkbox for electronic copy agreement supports efficient record distribution.


Collection Experience Feedback

This section gathers customer satisfaction data using multiple rating formats — star rating, matrix rating across seven service aspects, emotion rating and a 0–10 likelihood-to-return scale. The ranking question asking customers to prioritise seven potential improvements provides actionable service development input. The two open-ended questions about what was appreciated and what could be improved capture qualitative insights. The follow-up preference question closes the feedback loop.


Internal Review and Record Keeping

This section supports quality assurance and lifecycle management of the log. Fields for reviewer name, review date and review outcome (with follow-ups for corrections or additional information) enable supervisory oversight. The retention period question and storage location field support organised record management. The two checkboxes — confirming data minimisation practices and completion of all mandatory fields — reinforce operational discipline before the record is closed.


Confirmation and Signatures

The final section provides formal sign-off. The introductory paragraph clearly explains what the signatures confirm and notes that they do not replace separate agreements or receipts — an appropriate disclaimer. The mandatory confirmation checkbox, collector signature, printed name and timestamp create a clear acknowledgement of receipt. The staff member signature block mirrors this for the issuing side. The optional supervisor signature accommodates organisations with additional approval requirements. The final notes field allows for handover remarks and follow-up instructions.


Data Collection Implications

This form collects a substantial volume of data spanning identity information, transaction references, payment details, item-level records, condition assessments, exception logs and customer feedback. The breadth of data supports detailed operational reporting, fulfilment auditing, service quality monitoring and issue tracking. The structured choice fields and conditional follow-ups help maintain data consistency and reduce free-text variability. From a data-handling perspective, the form collects personal details including names, phone numbers, email addresses and potentially identity document references. The form itself includes appropriate reminders about data minimisation and internal handling procedures, which is a positive design choice. Organisations using this form should ensure their data retention, access control and disposal practices align with their own policies and applicable expectations in their jurisdiction.


User Experience Considerations

The form is logically sequenced, moving from administrative metadata through operational details to customer-facing elements and closing with sign-off. The use of conditional follow-ups throughout is a significant strength — it ensures staff only see relevant questions and keeps the form manageable despite its comprehensiveness. Placeholder examples in free-text fields provide helpful guidance. The inclusion of 'Not applicable' options in rating scales and 'No formal check performed' in identity verification demonstrates practical awareness of real-world variability. Potential friction points include the overall length of the form, which may be time-consuming for simple collections; the large number of mandatory fields across multiple sections; and the volume of personal data requested, which may require clear explanation to customers in some contexts. The form's structure mitigates these concerns through its clear section headings, instructional paragraphs and logical flow.


Overall Summary

This is a comprehensive and thoughtfully designed collection log that covers virtually every dimension of a counter handover process. Its strengths include clear logical sequencing, extensive use of conditional logic to keep questions relevant, well-chosen field types (single-choice, multiple-choice, matrix ratings, tables with calculated columns), helpful placeholder examples, and built-in accountability measures such as confirmation checkboxes and dual sign-off. The form balances operational depth with practical usability through its structured approach. Areas that organisations may wish to consider include whether the full depth of the form is necessary for every collection type — a lighter version for simple transactions could improve counter efficiency — and whether all personal data fields are needed for every use case, in line with data minimisation principles. Overall, the form provides a robust framework for documenting customer collections and counter handovers with a high degree of detail and traceability.


Mandatory Question Analysis for Customer Pickup and Counter Collection Log Form

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.


Mandatory Question Analysis

Log entry date and time
Recommendation: Requiring this field anchors each log record to a specific point in time, which supports chronological record-keeping and enables accurate sequencing when multiple collections occur on the same day. A timestamp is a foundational element for any operational log and helps when reviewing or investigating events later.


Log or reference number
Recommendation: Making this mandatory ensures each log entry can be uniquely identified and cross-referenced with other systems or records. A consistent reference scheme reduces the risk of duplicate or unidentifiable entries and supports efficient retrieval during audits or follow-up queries.


Staff member completing this log
Recommendation: Requiring this field establishes clear accountability for the log entry and identifies the point of contact if questions arise later. It supports internal quality oversight and helps trace responsibility across shifts or team members.


Type of collection
Recommendation: This mandatory single-choice field categorises the collection event, which supports operational reporting, process routing and analysis of collection patterns. The follow-up free-text field for the 'Other' option ensures unusual scenarios are still captured without forcing an inaccurate category selection.


Store, branch or collection point name
Recommendation: Requiring the site name ensures each record is attributed to a specific location, which is operationally important for multi-site organisations managing inventory, staffing and service quality across different collection points.


Order, ticket or transaction number
Recommendation: This mandatory field links the physical handover record to the underlying commercial transaction. It is a primary cross-reference key that supports order tracking, reconciliation and any subsequent customer enquiries about the collection.


Date the item became ready for collection
Recommendation: Requiring this date supports fulfilment timeline tracking and helps measure how long items wait before collection. It provides useful context when reviewing service levels or investigating delays.


Sales channel or point of order
Recommendation: This mandatory field identifies how the order originated, which supports channel performance analysis and helps staff understand the context of the collection. It can also inform process decisions if different channels have different fulfilment or payment workflows.


Customer full name
Recommendation: Requiring the customer's name ensures the record is associated with a specific individual and supports accurate record-keeping for the account holder or order owner. It is a basic identifier needed to match the collection to the correct customer record.


Collector full name (person at the counter)
Recommendation: Making this mandatory captures who physically received the items, which may differ from the customer. This distinction supports accurate handover records and helps resolve any later questions about who collected the items.


Is the collector the same person as the customer?
Recommendation: This mandatory yes/no question quickly identifies third-party collections, which may warrant different verification or documentation steps. The conditional follow-up explanation field captures the reason for proxy collection only when relevant, keeping the form efficient.


Customer phone number
Recommendation: Requiring a phone number provides a primary contact channel for follow-up communications about the collection, including notifications about outstanding items, payment issues or service feedback. Form administrators should consider whether a phone number is the preferred contact method for their customer base or whether alternative contact fields should also be required.


What was used to confirm the collector's identity?
Recommendation: This mandatory question documents the verification method used at the counter, which supports operational accountability and provides a record of the checks performed. The conditional follow-ups capture relevant details (such as document references or reasons for no check) only when applicable. The form appropriately frames this as a record-keeping measure rather than a legal requirement.


Total number of individual pieces handed over (including packaging units)
Recommendation: Requiring this summary figure provides a quick quantitative check on the handover and supports reconciliation against the item-level table above it. It is useful for inventory tracking and for verifying completeness at the point of release.


Total order value
Recommendation: Making the total order value mandatory ensures the financial context of the collection is always recorded. It supports payment reconciliation, reporting and any subsequent financial queries related to the transaction.


Balance collected at the counter
Recommendation: Requiring this field captures the amount actually paid at the time of collection, which is essential for accurate financial record-keeping and for identifying any outstanding balances. Together with the total order value, it supports clear payment tracking.


Overall condition of the consignment at handover
Recommendation: This mandatory single-choice field records the condition assessment at the point of release, which supports quality documentation and helps resolve any later disputes about item condition. The conditional follow-ups capture specific details about issues only when they are noted.


Was any discrepancy, delay or problem recorded during this collection?
Recommendation: Requiring this yes/no question ensures that exceptions are explicitly flagged rather than overlooked. It gates the subsequent detail fields so that issue information is captured only when relevant, supporting efficient exception tracking and follow-up.


I confirm that I have received the items listed in this log and that the details recorded are accurate to the best of my knowledge.
Recommendation: Making this confirmation checkbox mandatory ensures the collector explicitly acknowledges receipt and accuracy before the record is closed. It serves as a clear attestation point that supports the integrity of the handover record.


Collector signature
Recommendation: Requiring the collector's signature provides a formal acknowledgement of receipt and adds a layer of accountability to the handover record. It creates a clear point of confirmation that the items were received as documented.


Collector full name (printed)
Recommendation: Requiring the printed name alongside the signature ensures the record is legible and the collector is clearly identifiable, even if the signature itself is difficult to read. It supports accurate record-keeping and retrieval.


Date and time of collector signature
Recommendation: Requiring this timestamp records when the collector signed, which anchors the acknowledgement to a specific moment and supports chronological accuracy in the log.


Staff member signature
Recommendation: Requiring the staff member's signature creates a dual sign-off structure that documents both sides of the handover. It supports internal accountability and provides a balanced record of the transaction.


Staff member full name (printed)
Recommendation: The printed name ensures the staff member is clearly identified in the record, supporting legibility and accurate attribution of the handover action.


Date and time of staff signature
Recommendation: Requiring this timestamp completes the dual sign-off by recording when the staff member signed, ensuring both signatures are time-stamped for accurate record-keeping.


Overall Mandatory Field Strategy Recommendation

This form contains a significant number of mandatory fields — approximately twenty-five across twelve sections — reflecting its comprehensive scope as an end-to-end collection log. The mandatory fields are generally well-chosen and focus on core operational data: timestamps, reference numbers, identity details, financial figures, condition status, exception flags and formal sign-off. This approach ensures that every record contains the minimum information needed for a complete and traceable handover entry.


Balancing data depth and completion rates: While the mandatory field selection is logical, the overall number of required fields may create friction during busy counter periods or for straightforward collections. Organisations may wish to consider whether a streamlined version of the form — with fewer mandatory fields — could be used for simple, low-value or routine collections, reserving the full form for complex or high-value transactions. This tiered approach could improve completion speed without sacrificing record quality for the cases that need it most.


Conditional logic: The form already makes excellent use of conditional follow-ups throughout, which helps keep the experience relevant and reduces unnecessary data entry. Extending this principle to some mandatory fields — for example, making financial fields mandatory only when a payment is involved, or making identity verification fields mandatory only when a formal check is performed — could further reduce friction while maintaining data quality.


Placement and flow: The mandatory fields are distributed across the form in a logical sequence, with administrative metadata at the start and formal sign-off at the end. This placement supports a natural workflow and ensures that critical data is captured at the appropriate stage. The confirmation checkboxes near the end — including one explicitly verifying that all mandatory fields have been completed — are a strong closing control that supports data completeness before the record is closed.


General best practices: Organisations should periodically review their mandatory field selections based on actual usage patterns, staff feedback and any changes to their operating procedures. Fields that are consistently left blank or that cause delays may warrant reconsideration. Conversely, if certain optional fields are consistently completed, they may be candidates for mandatory status. The form's disclaimer that it is a general-purpose aid — not a legal or regulatory instrument — is appropriate, and organisations should adapt the mandatory field set to their own operational needs and local expectations.


Editing this form is like giving a high-five to the future—make it legendary! ✋🚀 Edit this Customer Pickup and Counter Collection Log Form
Hello folks! Ready to turn data headaches into clear insights? Zapof's auto-calculating tables and spreadsheet capabilities are your trusty sidekicks for insightful analysis, making your job easier.
This form is protected by Google reCAPTCHA. Privacy - Terms.
 
Powered by Zapof